ERR_NAME_NOT_RESOLVED: How to Fix It Fast

by
DNS lookup failing so the browser cannot find the website
ERR_NAME_NOT_RESOLVED means the browser could not turn the domain name into an IP address

ERR_NAME_NOT_RESOLVED appears when your browser cannot resolve a domain name into an IP address. The request fails at the DNS level, so the website cannot be found.

This is usually a DNS or network issue. In most cases the problem is local, not on the website itself. A typo, a dead DNS resolver, or a stale cache is enough to trigger it.

Quick Fix

  • Check the URL for typos.
  • Restart your router and device.
  • Flush the DNS cache.
  • Switch to Google DNS (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1).
  • Disable VPN or proxy.
  • Clear browser cache and try another network.

These steps fix most ERR_NAME_NOT_RESOLVED errors within minutes.

What ERR_NAME_NOT_RESOLVED Actually Means

Browser unable to resolve a domain name through DNS
DNS translates a domain name into an IP. If that lookup fails, the browser stops

Every website has an IP address. DNS (Domain Name System) translates the domain name into that address.

When you open a website, your browser asks a DNS server what IP belongs to the domain. If the DNS server cannot answer, Chrome shows ERR_NAME_NOT_RESOLVED. The browser has no way to locate the server.

The failure can happen at different levels:

  • The domain name is mistyped or does not exist
  • DNS records or nameservers are missing
  • Your device cannot reach the DNS server

Why ERR_NAME_NOT_RESOLVED Happens

Incorrect Domain Name

A single wrong character in the URL is enough to trigger this error.

DNS Server Not Responding

The DNS server may be offline, overloaded, or blocked by the network.

Missing DNS Records

If the domain has no A record or its nameservers are wrong, it cannot resolve.

Local DNS Cache Issues

Your system may store an outdated or broken DNS answer.

VPN or Proxy Interference

Some VPN services use unstable DNS and fail the lookup.

Firewall or Antivirus Blocking DNS

Security software can block DNS queries on port 53.

Domain Expired or Not Registered

If the domain is inactive, resolution fails everywhere, not only on your device.

Step-by-Step Fixes

1. Check the Domain Name

Confirm the URL is typed correctly. Even one wrong character causes a DNS failure. Also try the site with and without www.

Restarting network equipment to clear a failed DNS lookup
Restarting the router clears a stuck DNS path that often causes this error

2. Restart Your Router and Device

Turn the router off for 30–60 seconds, plug it back in, then restart the computer and reconnect. This clears temporary network and resolver issues.

3. Flush DNS Cache

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

4. Change DNS Servers

Switch to a reliable public DNS:

  • Google DNS: 8.8.8.8 and 8.8.4.4
  • Cloudflare DNS: 1.1.1.1 and 1.0.0.1

This often fixes a dead or slow ISP resolver immediately.

5. Disable VPN or Proxy

Quit the VPN app completely and turn off any proxy, then test again. They can replace your DNS and break resolution.

6. Check the Hosts File

The hosts file can override DNS. On Windows check C:\Windows\System32\drivers\etc\hosts. On macOS and Linux check /etc/hosts. Remove incorrect entries for the domain.

7. Reset Network Settings

Windows (Command Prompt as Administrator):

netsh int ip reset
netsh winsock reset

Restart the computer after these commands.

Advanced Troubleshooting

Testing domain DNS records after a name resolution failure
If the domain fails on every network, the DNS records or the registration are the problem

Use nslookup

nslookup example.com

If no IP address is returned, DNS is failing. Compare the result against nslookup example.com 1.1.1.1 to see whether only your resolver is broken.

Test Another Network

Switch to mobile data or another Wi-Fi network. If the site works there, the issue is your network or resolver.

Check Domain DNS Records

If you own the site, verify the A or AAAA record and the nameservers at the registrar. A recent nameserver change with an empty zone causes this error for everyone.

Check Domain Status

Confirm the domain is registered and not expired. An expired domain cannot resolve.

Does ERR_NAME_NOT_RESOLVED Affect SEO?

Yes, if your own domain cannot resolve. Search engines cannot crawl the site, pages can drop from the index, and traffic falls until DNS is restored. Fix a public DNS failure immediately.

How to Prevent This Error

  • Use reliable DNS providers
  • Monitor domain expiration
  • Verify DNS records after every change
  • Avoid unstable VPN DNS
  • Keep the hosts file free of old overrides

When to Contact Support

Contact your registrar or host if the domain does not resolve anywhere, DNS records are missing, or nameserver changes never propagate. They can confirm the zone and registration status.

Related DNS Errors

FAQ

What does ERR_NAME_NOT_RESOLVED mean?

The domain could not be resolved to an IP address through DNS.

Is this a website problem?

Usually no. It is often a local DNS or network issue. If it fails on every network, then the domain records or registration are the problem.

Can changing DNS fix it?

Yes. Switching to Google or Cloudflare DNS often resolves a bad ISP resolver.

Can a VPN cause this error?

Yes. VPN DNS can fail the lookup even when the domain is fine.

How fast can it be fixed?

Most local cases are resolved within a few minutes. A missing public DNS record depends on the registrar.

Summary

ERR_NAME_NOT_RESOLVED occurs when a domain name cannot be translated into an IP address.

The most common causes are a typo, a dead DNS resolver, cache, or a missing record. Restart the network, flush DNS, and switch DNS servers first. If the domain fails everywhere, check nameservers and registration.

Main Error Hub

For a full list of DNS, SSL, server, and WordPress issues, see the complete website error guide.

Leave a Comment