ERR_NAME_NOT_RESOLVED: What It Means and How to Fix It

ERR_NAME_NOT_RESOLVED is Chrome's error for a DNS lookup failure. It means the browser tried to find the IP address for a domain name and couldn't — the domain name couldn't be "resolved" to an address the browser could connect to.

It's similar to DNS_PROBE_FINISHED_NXDOMAIN but slightly broader. NXDOMAIN specifically means the domain doesn't exist in DNS. ERR_NAME_NOT_RESOLVED can also include cases where the DNS server itself is unreachable or taking too long to respond.

What Causes ERR_NAME_NOT_RESOLVED?

1. The Domain Doesn't Exist

A typo in the URL, a domain that's never been registered, or a domain that has expired and been deleted from DNS will all produce this error. The DNS query comes back empty.

If you own the site, check that your domain registration is current. Domain expiry monitoring is the easiest way to make sure you never accidentally let a domain lapse.

2. DNS Server Is Unreachable

If your device can't reach its configured DNS server — because of a network outage, a misconfigured router, or a DNS server that's down — you'll get this error for every domain you try.

A quick test: if multiple sites are failing with ERR_NAME_NOT_RESOLVED at the same time, your DNS server is likely the issue, not a specific website.

3. Stale DNS Cache

Your device and browser cache DNS results to speed up future lookups. If a domain's DNS records changed recently and your cached entry hasn't expired yet, your browser may be looking up an old or invalid address.

4. DNS Propagation Not Yet Complete

If you've recently updated DNS records or changed nameservers, the changes take time to propagate across the internet. During this window, some DNS servers will still serve the old records while others have the new ones.

This means the site might load fine on some networks but produce ERR_NAME_NOT_RESOLVED on others. See our guide on DNS TTL to understand how propagation works.

5. VPN or Proxy DNS Leak

Some VPN configurations route your traffic through the VPN but resolve DNS through your regular ISP. If the VPN connection drops or the DNS routing breaks, name resolution can fail for sites only accessible via that DNS path.

6. Hosts File Override

An entry in your computer's hosts file that maps a domain to an IP address that no longer exists can cause ERR_NAME_NOT_RESOLVED. Check:

• macOS/Linux: /etc/hosts
• Windows: C:\Windows\System32\drivers\etc\hosts

How to Fix ERR_NAME_NOT_RESOLVED

Flush Your DNS Cache

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Linux:

sudo systemd-resolve --flush-caches

Also clear Chrome's internal DNS cache at chrome://net-internals/#dns.

Switch to a Different DNS Server

Your ISP's DNS might be slow, unreliable, or not yet reflecting recent DNS changes. Switch to a public resolver:

Google DNS: 8.8.8.8 / 8.8.4.4 Cloudflare DNS: 1.1.1.1 / 1.0.0.1

On macOS: System Settings > Network > your connection > Details > DNS. On Windows: Network adapter properties > IPv4 settings.

Verify Your Internet Connection

If multiple sites are failing, check your router, confirm other devices on the same network are affected, and restart your modem/router if needed.

Check the Domain's DNS Records

If you own the site, verify your DNS configuration is correct:

dig yourdomain.com
nslookup yourdomain.com 8.8.8.8

Compare the result with what your DNS provider shows in its dashboard. If the records are missing or wrong, fix them there.

Disable VPN or Proxy

Disconnect from any VPN or proxy and try again. If the error goes away, your VPN's DNS configuration is the culprit — check its DNS settings or contact your VPN provider.

For Website Owners: Preventing DNS-Related Outages

ERR_NAME_NOT_RESOLVED from the server side almost always comes down to one of three things: an expired domain, a misconfigured DNS record, or DNS propagation. All three are manageable:

1. Monitor domain expiry — get alerted weeks before it lapses
2. Double-check DNS records after any hosting migration or nameserver change
3. Use low TTLs before making DNS changes so propagation is faster when you need to switch

Domain Monitor monitors your domain expiry and alerts you well in advance, so a forgotten renewal never takes your site offline.

Related Articles

• DNS_PROBE_FINISHED_NXDOMAIN - What It Means and How to Fix It
• ERR_CONNECTION_REFUSED - What It Means and How to Fix It
• ERR_SSL_PROTOCOL_ERROR - What It Means and How to Fix It