Error guide / ERR_NAME_NOT_RESOLVED

ERR_NAME_NOT_RESOLVED error

ERR_NAME_NOT_RESOLVED appears when the browser can't turn a site's name into an IP address. The DNS lookup returned nothing, so Chrome has no server to connect to and shows that the site can't be reached. Unlike NXDOMAIN, the cause isn't always a missing domain; it can also be your network or DNS resolver.

What causes it

It's either the domain's DNS (no matching record, changed NS, brand-new domain) or your local setup: an unreachable resolver, a block, a stale cache, or a VPN. If the site fails only for you, look at your own connection first.

How to fix it

1. Open the site from another network or your phone's mobile data; if it loads there, the problem is local.
2. Flush the DNS cache: on Windows run ipconfig /flushdns, then restart the browser.
3. Temporarily switch your DNS to a public resolver (for example 1.1.1.1 or 8.8.8.8) and try again.
4. Disable VPN, proxy and blocker extensions; they sometimes break name resolution.
5. If it fails for everyone, check the domain's DNS: it needs an A record pointing to the server IP. In cPanel that's the Zone Editor.
6. Run the domain through the check below to see whether the name resolves from the public internet.

Related errors

• DNS_PROBE_FINISHED_NXDOMAIN DNS_PROBE_FINISHED_NXDOMAIN error
• DNS_PROBE_FINISHED_NO_INTERNET DNS_PROBE_FINISHED_NO_INTERNET error
• This site can't be reached This site can't be reached
• Домен не резолвиться після зміни NS Domain not resolving after an NS change or migration