What Is ERR_NAME_NOT_RESOLVED and How Do You Fix It?

ERR_NAME_NOT_RESOLVED is a DNS error showing that the browser could not translate the domain name of the site you want to visit into an IP address. Chrome then shows the message “… server IP address could not be found” on the “This site can’t be reached” page, together with the code ERR_NAME_NOT_RESOLVED. In this guide we explain what the error means, what causes it and how to fix it on a computer, on a phone and as a site owner.

What Does ERR_NAME_NOT_RESOLVED Mean?

Every site on the internet runs at an IP address; domain names exist to make these addresses easy to remember. When you open a site, your device first asks a DNS server, “what is the IP address of this domain?” If the DNS server cannot answer, answers wrongly, or the domain’s record cannot be found, the browser does not know which server to connect to and the ERR_NAME_NOT_RESOLVED error appears. In short, the problem is not the site itself but the step where the name is translated into an address.

Causes of the ERR_NAME_NOT_RESOLVED Error

• The address is mistyped: A single wrong letter in the domain makes the device look up a name that does not exist.
• The DNS server is not responding: The DNS service of your internet provider or router may be temporarily down.
• Stale DNS cache: Your device or browser may remember an old record for the domain that is no longer valid.
• The domain has expired or has no DNS record: If the domain was not renewed or its A record was deleted, no DNS server can return an IP address.
• A nameserver change has not propagated yet: If the domain’s DNS servers were changed recently, the record may not be found on some networks for a while.
• Security software, VPN or a custom DNS setting: An app that filters DNS queries, or a mistyped custom DNS address, can block the lookup.

How to Fix ERR_NAME_NOT_RESOLVED on a Computer

1. Check the Address and Your Internet Connection

Make sure the domain in the address bar is spelled correctly and see whether other sites open. If no site opens, restart your router.

2. Flush the DNS Cache

On Windows, open Command Prompt as administrator and run these commands:

ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew
netsh winsock reset

Then restart the computer. To clear Chrome’s own DNS cache, type chrome://net-internals/#dns in the address bar and click Clear host cache.

3. Change Your DNS Server

The most common lasting fix is to use a reliable public DNS instead of your internet provider’s DNS. On Windows, go to Control Panel > Network and Sharing Center > Change adapter settings and enter these addresses in the Internet Protocol Version 4 (TCP/IPv4) properties of your connection:

Provider	Preferred DNS	Alternate DNS
Google	8.8.8.8	8.8.4.4
Cloudflare	1.1.1.1	1.0.0.1
Quad9	9.9.9.9	149.112.112.112

4. Check Secure DNS in Chrome

In Chrome, if Settings > Privacy and security > Security > Use secure DNS is on with a specific provider selected, turn it off temporarily or switch it to “With your current service provider” and try again. You can also turn extensions off or use an incognito window to see whether an extension is interfering with lookups.

5. Check VPN, Proxy and Security Software

If you use a VPN or proxy, turn it off and try again. The web protection feature of an antivirus or firewall may be blocking DNS queries; turn it off temporarily to test. Also check that the hosts file has no faulty line for the domain.

ERR_NAME_NOT_RESOLVED on Android and iPhone

• Android: Clear Chrome’s cache under Settings > Apps > Chrome > Storage > Clear cache. If a manual address is entered under Settings > Network & internet > Private DNS, make sure it is correct or switch it to “Automatic”.
• iPhone: Turn airplane mode on and off. In the Wi-Fi network’s details, if Configure DNS is set to “Manual”, switch it to “Automatic” or enter a reliable DNS address.
• On both systems, switch between Wi-Fi and mobile data to test whether the network is the cause.

What Is DNS_PROBE_FINISHED_NO_INTERNET and How Is It Different?

DNS_PROBE_FINISHED_NO_INTERNET shows that Chrome could not perform a DNS lookup because there is no internet connection at all. With ERR_NAME_NOT_RESOLVED the internet usually works but a particular domain cannot be resolved; with DNS_PROBE_FINISHED_NO_INTERNET the device cannot reach the internet at all. To fix it, first check the Wi-Fi or cable connection, the router and the network adapter; on Windows, the network troubleshooter and the netsh winsock reset command bring the connection back in most cases. For the case where the domain cannot be found at all, see our article on the DNS_PROBE_FINISHED_NXDOMAIN error, and for the case where the DNS server does not answer at all, see DNS server not responding.

For Site Owners: If Your Site Returns ERR_NAME_NOT_RESOLVED

If your site shows this error on other networks and devices too, the problem is in your domain’s DNS configuration:

1. Check the domain’s expiry: DNS is suspended for expired domains. Check the renewal date in your registrar’s panel.
2. Verify the nameservers: Make sure the domain points to the DNS servers where your records are kept.
3. Check the A and CNAME records: Verify that a record exists for the root domain and for www, and that it points to the correct IP address. On the command line, nslookup yourdomain.com 8.8.8.8 shows the result.
4. Wait for propagation: After a nameserver or record change, the update does not reach all networks immediately; depending on the records’ TTL it can take a few hours.

Conclusion

ERR_NAME_NOT_RESOLVED is a DNS error showing that the domain could not be translated into an IP address. On the visitor side, checking the address, flushing the DNS cache and switching to a reliable public DNS usually solves the problem. If the site does not open for anyone, check the domain’s expiry, the nameserver settings and the DNS records.