ERR_NAME_NOT_RESOLVED: 7 Quick Fixes in Chrome

ERR_NAME_NOT_RESOLVED is a DNS error. Chrome could not turn the website name into an IP address, so it says “This site can’t be reached” and “server DNS address could not be found”. Fixing ERR_NAME_NOT_RESOLVED usually means fixing your DNS settings.

Quick answer: ERR_NAME_NOT_RESOLVED is a DNS failure. Flush your DNS cache, change your DNS servers to 8.8.8.8 and 1.1.1.1, restart the DNS Client service, and turn off any VPN or proxy.

ERR_NAME_NOT_RESOLVED error message shown in Chrome browser

What Causes ERR_NAME_NOT_RESOLVED?

DNS works like a phone book. When the lookup fails you see this error. Common reasons:

The domain was typed wrong or has expired.
Your DNS server is slow, down or blocked.
The DNS cache on your computer is corrupted.
A VPN, proxy or hosts file entry is overriding DNS.

How to Fix ERR_NAME_NOT_RESOLVED: Step-by-Step

Step 1: Check the address

Make sure the domain is spelled correctly and still exists. Try it on your phone with mobile data.

Step 2: Flush DNS

Open Command Prompt as administrator and run ipconfig /flushdns, then ipconfig /registerdns.

Also Read: https://axeetech.com/how-to-fix-dns-probe-finished-nxdomain-complete-guide/

Step 3: Change your DNS servers

Open Network Connections, right-click your adapter, Properties, Internet Protocol Version 4, and set 8.8.8.8 and 8.8.4.4 or 1.1.1.1 and 1.0.0.1.

Step 4: Restart the DNS Client service

Press Win+R, type services.msc, find DNS Client, and restart it. If it is greyed out, restart the PC instead.

Step 5: Turn off VPN and proxy

Disconnect anything that reroutes traffic. The related error DNS_PROBE_FINISHED_NXDOMAIN often goes away with the same steps.

Step 6: Clear Chrome’s internal DNS cache

Visit chrome://net-internals/#dns and click Clear host cache. Then close and reopen Chrome.

Step 7: Restart the router

Restart your router so it refreshes its own DNS cache. See Google’s public DNS guide for setup help on any device.

ERR_NAME_NOT_RESOLVED on Mac, Android and iPhone

On a Mac, flush DNS with sudo dscacheutil -flushcache and sudo killall -HUP mDNSResponder, then set DNS servers under System Settings, Network, Details, DNS. The Apple Support site documents the menus.

On Android, set Private DNS to dns.google under Settings, Network & internet. On iPhone, choose Configure DNS on your Wi-Fi network and add 1.1.1.1. If it only fails on one Wi-Fi network, restart that router.

Advanced Troubleshooting for ERR_NAME_NOT_RESOLVED

Test DNS directly. In Command Prompt run nslookup example.com and then nslookup example.com 8.8.8.8. If the second works and the first fails, your default DNS server is the problem and you should switch permanently.

Disable IPv6 temporarily in the adapter properties if lookups still fail. Some routers handle IPv6 DNS poorly, and turning it off for a test shows whether it is the cause.

Chrome’s secure DNS setting can also interfere. Open chrome://settings/security, scroll to Use secure DNS, and try switching the provider or turning it off. Microsoft documents DNS client behaviour in its Windows support center. Related reads: DNS_PROBE_FINISHED_NXDOMAIN and ERR_CONNECTION_TIMED_OUT.

ERR_NAME_NOT_RESOLVED fix checklist with steps in order

How to Stop ERR_NAME_NOT_RESOLVED Coming Back

Use a fast public DNS.
Avoid editing the hosts file without a reason.
Keep your router firmware updated.

Common Mistakes When Fixing ERR_NAME_NOT_RESOLVED

Most repeat cases of ERR_NAME_NOT_RESOLVED come from a handful of avoidable slips. Before you spend an hour on advanced troubleshooting, check that you have not made one of these:

Typing a public DNS address with a typo, such as 8.8.8.4 instead of 8.8.8.8 or 8.8.4.4.
Forgetting to restart the browser after changing DNS, so cached failures remain.
Assuming the website is deleted before testing it on another network.

Testing one change at a time also helps. If you change DNS, proxy and firewall settings together, you will not know which change actually fixed ERR_NAME_NOT_RESOLVED, and you may leave a harmful setting in place.

Quick Recap: Fixing ERR_NAME_NOT_RESOLVED

Work through the fixes in order, because most cases of ERR_NAME_NOT_RESOLVED clear up within the first three or four steps. If you still see ERR_NAME_NOT_RESOLVED after every step, note the time it happens, which network you are on, and which sites are affected, then contact your internet provider, your hosting company or the site owner with those details.

How to fix ERR_NAME_NOT_RESOLVED in Chrome step-by-step guide

ERR_NAME_NOT_RESOLVED FAQ

What is ERR_NAME_NOT_RESOLVED?

A Chrome error meaning the domain name could not be turned into an IP address by DNS.

Does it mean the site is deleted?

Not always. It can also be your DNS or network. Test on another network.

Will changing DNS slow my internet?

No. A good public DNS is often faster than the default one from your ISP.

Is ERR_NAME_NOT_RESOLVED the same as NXDOMAIN?

They are close. NXDOMAIN means DNS answered that the domain does not exist, while NAME_NOT_RESOLVED means Chrome could not get a usable answer at all.

Which DNS is best for fixing it?

Google (8.8.8.8) and Cloudflare (1.1.1.1) are fast and reliable choices that fix most lookup failures.

Axee Davies

Axee Davies is the founder of AxeeTech, publishing gaming guides, codes, and Windows how-tos since March 2013. A tech enthusiast for 13+ years — starting with smartphones and Android rooting — he now runs a site that puts out a new guide every day for Roblox players, traders, and Windows users. More about AxeeTech

axeetech.com