ERR_NAME_NOT_RESOLVED
Plain-English meaning
Browser cannot resolve the hostname to an IP address, so it cannot open a connection.
Why it happens
DNS lookup fails before TCP/TLS starts. Missing DNS record, typoed hostname, broken DNS delegation, or resolver/network outage.
Common causes
- Missing A/AAAA/CNAME for hostname
- Typo in app or browser URL
- Nameserver delegation/zone misconfiguration
- Resolver outage or split-horizon mismatch
What to check first
Run dig/nslookup against authoritative and public resolvers, verify exact hostname requested, and confirm DNS propagation/TTL behavior.
How to fix it
Create or correct DNS records, fix hostname typos in configs, and repair NS delegation or zone settings at your DNS provider.
Example signal
net::ERR_NAME_NOT_RESOLVED DNS_PROBE_FINISHED_NXDOMAIN
Related links
ERR_CONNECTION_REFUSED · ERR_CERT_COMMON_NAME_INVALID · Cloudflare 522 · Cloudflare 524