Ad Space — Top Banner

ERR_NAME_NOT_RESOLVED

Universal DNS/Network

Severity: Moderate

What Does This Error Mean?

ERR_NAME_NOT_RESOLVED means your browser could not translate the website's name into an address. Every website has a numeric address (called an IP address), and DNS is the system that finds it. When that lookup fails, you see this error. The website name could not be resolved — meaning found and matched to an address.

Affected Models

  • Google Chrome
  • Microsoft Edge
  • Opera
  • Brave
  • Chromium-based browsers
  • Windows
  • macOS

Common Causes

  • The domain name was typed incorrectly
  • Your DNS server is down or not responding
  • Your DNS cache has an outdated or corrupted entry for this site
  • A firewall or security software is blocking DNS requests
  • The website's domain has expired or been taken offline

How to Fix It

  1. Check the web address for typos. Make sure the spelling, dots, and extension (.com, .org, .net) are all correct.

    A single wrong letter is enough to cause this error.

  2. Flush your DNS cache. On Windows, open Command Prompt and type: ipconfig /flushdns — then press Enter. On Mac, type: sudo dscacheutil -flushcache and press Enter.

    Old cached entries can point to the wrong address. Flushing forces a fresh lookup.

  3. Restart your router and modem. Unplug them from the wall, wait 30 seconds, and plug them back in.

    Your router also holds a DNS cache. A restart clears it.

  4. Switch your DNS server to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google). Go to your network adapter settings, open IPv4 Properties, and enter one of those addresses manually.

    Your ISP's DNS server may be having problems. A public DNS server is a reliable alternative.

  5. Temporarily disable your VPN, antivirus, or firewall and try loading the site again. If it works, one of those tools is blocking the DNS request.

    Re-enable your security software after testing and adjust its settings to allow the site.

When to Call a Professional

If all troubleshooting steps fail and multiple websites cannot be reached, contact your ISP. If you are on a corporate network, speak to your IT department — they control the DNS settings on work machines.

Frequently Asked Questions

Is ERR_NAME_NOT_RESOLVED the same as DNS_PROBE_FINISHED_NXDOMAIN?

They are very similar — both mean the DNS lookup failed. ERR_NAME_NOT_RESOLVED is a broader Chrome error for any DNS failure. DNS_PROBE_FINISHED_NXDOMAIN specifically means the domain genuinely does not exist in the DNS system. The fixes for both are the same.

Does this error mean the website is down?

Not necessarily. The error means your device could not find the address for the site. The site itself could be fine — the issue is with how your device is looking it up. Try visiting the site on your phone with mobile data to see if the site is up.

Can a VPN cause ERR_NAME_NOT_RESOLVED?

Yes, very commonly. VPNs route your DNS requests through their own servers. If the VPN server is down, misconfigured, or blocking certain domains, you will see this error. Disconnect your VPN and try again to confirm whether it is the cause.