ERR_NAME_NOT_RESOLVED

How to Fix “ERR_NAME_NOT_RESOLVED”

DNS Error 📄 Chrome, Edge, Brave
⚡ Quick answer

ERR_NAME_NOT_RESOLVED means Chrome could not resolve the domain name to an IP address. It is closely related to DNS_PROBE_FINISHED_NXDOMAIN and is caused by DNS failures, no internet connection, or a mistyped URL.

First, check if your internet is working and what your current IP address is:

🔍 Check My IP Address →

What Causes the “ERR_NAME_NOT_RESOLVED” Error?

This error is Chrome's generic DNS resolution failure message. When you type a URL, Chrome asks a DNS server to translate the domain name into an IP address. ERR_NAME_NOT_RESOLVED means that translation failed completely — the DNS server either could not be reached, did not know the domain, or returned an error. Common causes include: no internet connection, wrong DNS server configured, corrupted DNS cache, mistyped URL, or the domain genuinely does not exist.

How to Fix It — 5 Methods

1 Verify your internet connection ▶

Check you are connected to the internet before anything else.

  1. Try loading google.com — if it works, your internet is fine and the problem is with the specific site
  2. Check your Wi-Fi or ethernet is connected
  3. Restart your router if all sites fail
2 Flush DNS cache ▶

Windows: Open Command Prompt as Administrator and run ipconfig /flushdns
Mac: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Restart your browser after flushing.

3 Switch to Google or Cloudflare DNS ▶

Set your DNS to a reliable public server.

  1. Windows: Settings → Network → Change adapter options → right-click connection → Properties → IPv4 → set DNS to 8.8.8.8 and 8.8.4.4
  2. Mac: System Settings → Network → DNS → add 8.8.8.8 and 1.1.1.1
  3. Restart your browser
4 Clear Chrome's internal DNS cache ▶

Chrome keeps its own internal DNS cache separate from the system cache.

  1. In Chrome, go to chrome://net-internals/#dns
  2. Click "Clear host cache"
  3. Then go to chrome://net-internals/#sockets
  4. Click "Flush socket pools"
  5. Try the site again
5 Use a VPN to bypass DNS blocks ▶

If the site works on mobile data but not your home network, your ISP is blocking it. A VPN uses its own DNS and bypasses the block.

  1. Connect to PureVPN or IPVanish
  2. Try loading the site again
🔒
Some errors are caused by ISP blocks or network restrictions
A VPN bypasses them instantly by routing through a different server.
PureVPN → IPVanish →

✅ Fixed it? Visit tools.examineip.com to confirm your IP address and connection are working correctly.

Frequently Asked Questions

What is the difference between ERR_NAME_NOT_RESOLVED and DNS_PROBE_FINISHED_NXDOMAIN?
They are very similar. ERR_NAME_NOT_RESOLVED is a general DNS failure. DNS_PROBE_FINISHED_NXDOMAIN is more specific — it means the DNS server responded but said the domain does not exist. The fixes for both are the same.
Can ERR_NAME_NOT_RESOLVED be caused by my antivirus?
Yes. Some antivirus programs intercept DNS queries and can block them incorrectly. Try temporarily disabling your antivirus to test — if that fixes it, add the site to your antivirus whitelist.
Does ERR_NAME_NOT_RESOLVED mean the site is hacked or dangerous?
No. This error is purely a DNS connectivity issue. It has nothing to do with the security of the site you are trying to reach.

Learn More About IP Addresses & Privacy

Other Internet Errors Explained

DNS_PROBE_FINISHED_NXDOMAIN
This error means your browser could not find...
Server IP address could not be found
This error means Chrome tried to look up...
ERR_CONNECTION_TIMED_OUT
ERR_CONNECTION_TIMED_OUT means your browser sent a request to...

← Back to the complete guide: Internet Errors Hub

Last updated: March 30, 2026 • Report an error

Scroll to Top