How to Fix ERR_NAME_NOT_RESOLVED in Chrome

Chrome shows ERR_NAME_NOT_RESOLVED when your device asks a DNS server to turn a website name into an address and gets no answer. The page says the server’s DNS address could not be found. The problem is usually a typo, a DNS hiccup or a bad DNS setting, and it is rarely the website itself.

What causes ERR_NAME_NOT_RESOLVED

• The address was typed wrongly, or the domain no longer exists.
• Your internet connection is down or unstable.
• A stale or damaged DNS cache on your device.
• Your provider’s DNS server is slow or not responding.
• A VPN, proxy or security tool is interfering.
• A wrong entry in the hosts file.

1. Check the address and test other sites

Look at the address for spelling mistakes and make sure the ending, such as .com, is right. Then open a different website. If every site fails, your connection or DNS is the problem. If only one site fails, the problem may be that site’s domain, so try it on your phone using mobile data to confirm.

2. Restart the router

Unplug the router and modem for about 30 seconds, plug them back in and wait a few minutes. Then try again.

3. Flush the DNS cache

On Windows, right-click the Start button, choose Terminal (Admin) or Command Prompt (Admin) and run:

ipconfig /flushdns

On a Mac, open Terminal and run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Reopen Chrome and try the site again.

4. Switch to a different DNS server

In Windows 11 open Settings > Network & internet, choose Wi-Fi or Ethernet, open your connection’s properties, and next to DNS server assignment select Edit, then Manual and turn on IPv4. You can enter a public resolver such as Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1). Save and retest.

5. Turn off VPN, proxy and extensions

Disconnect any VPN and test again. In Windows, check Settings > Network & internet > Proxy and turn off any proxy you do not recognise. Open the site in an Incognito window, which disables most extensions, to see whether an extension is the cause.

6. Check the hosts file

The Windows hosts file at C:WindowsSystem32driversetchosts can send a site name to the wrong place. Open it in Notepad as administrator and look for lines that mention the site and are not marked with a leading #. Only remove entries you added or recognise, and save a copy first.

7. If you own the website

Confirm the domain has not expired, that its nameservers are correct at the registrar, and that the DNS records, especially the A record, point to your server. DNS changes can take time to spread, sometimes several hours.

Frequently asked questions

Is ERR_NAME_NOT_RESOLVED a virus?

No. It is a DNS lookup failure. Check for security software issues only if other odd things are happening too.

Why does it work on my phone but not my laptop?

Your laptop likely has a damaged DNS cache or a different DNS setting. Steps 3 to 6 target those.

Related Chrome errors: ERR_CONNECTION_FAILED and ERR_NO_BUFFER_SPACE.

When to contact support

If every device fails after the router restart, contact your internet provider. If you own the site and the domain settings look right, contact your domain registrar or hosting provider. See our Wi-Fi and internet overview for wider connection checks.