Fix ERR_NAME_NOT_RESOLVED Error in Chrome
Err_name_not_resolved error happens when your browser can’t find the IP address that matches with the hostname of the target website. There are many possible causes why this could happen to you. We have explained in detail about resolving host concept and fixing the issue in Chrome. A very common reason is that you don’t have reliable network connection, corrupted DNS, due to ISP issues, faulty router, damaged cables and others.
In some cases, virus or malware activity can become the cause of this error.
Viewing Cached Copy of a Page
The error message on Chrome will look like something below showing the DNS address couldn’t be found for the site.
As you can see there are two options offered in the error message. One is to search Google for the site and the second is to view cached copy of the site. Click on the “Show saved copy” button to view the copy the page already available in Google’s cache.
The cached page may not be the latest version, but in most cases will have the same content what you are looking for. There are no universal solutions to fix err_name_not_resolved error. You may try any of the solutions below to check it helps to view the webpage directly from the server.
Solution 1: Clear Cookies and Cache
Removing cache and cookies should be a good way to fix many errors. This is among the first thing you should do. Bad downloaded files could cause Err_name_not_resolved error in your system, so this solution may resolve the problem. Follow these steps:
- Open Chrome web browser, type the command URL on the address bar - "chrome://settings/clearBrowserData" and hit Enter.
- Make sure that options for removing cookies and cache are checked. You don’t have to remove login information. Click on the "Clear Data" button.
- Wait for a few minutes and restart your browser. Verify that the problem has been resolved.
Solution 2: Flush DNS Cache
It is another common way for eliminating Chrome related problems, including err_name_not_resolved error. It is easy to do by following the below steps:
- Press "Win + X" to open power user or quick access menu.
- Select the option "Command Prompt (Admin) to make sure that you have administrative privilege to run commands.
- Type in these commands one by one and hit Enter after typing each:
- ipconfig /flushdns > Enter.
- ipconfig /renew > Enter.
- ipconfig /registerdns > Enter.
- If successful, your old DNS cache will be erased and IP address renewed. Restart your web browser and check whether the problem has been resolved.
Learn more about viewing and flushing DNS.
Solution 3: Change Default DNS Server with OpenDNS or Google DNS
You should do this solution after clearing the DNS cache, with the above steps. If you are using a DNS server with bad configuration, err_name_not_resolved error may appear. With OpenDNS or Google DNS, you are guaranteed to get reliable DNS servers. Follow these steps to change the DNS:
- Open "Control Panel" and click on the "Network and Sharing Center" icon.
- After the windows opens, look for “Change adapter settings” option and click on it.
- Right click on your active network adapter and choose "Properties" from the context menu
- Look for "Internet Protocol Version (TCP/IPv4)" and double click on it.
- Type in 184.108.40.206 for the Preferred DNS server and 220.127.116.11 for Alternate DNS server if you use want to Google DNS.
- Type in 18.104.22.168 for the Preferred DNS server and 22.214.171.124 for Alternate DNS server if you want to use OpenDNS
- Click OK and restart your Chrome browsers
Solution 4: Restart Router
If you haven’t switched off your router for months, then it may start to accumulate a lot of glitches. Restarting your router is a good way to start anew. Follow these steps:
- Don’t press the Power button, unplug your router to shut it down completely.
- Shut down your computer.
- Wait for a few minutes and turn your router and computer back on.
- Open your Chrome browser and verify that the problem has been resolved.
Solution 5: Check Firewall Settings
Check whether your firewall settings are too restrictive. If this is the case, there’s a good chance that your web browsers will be blocked and can’t access a lot of websites, resulting in err_name_not_resolved error. An easy way to do this is to disable your firewall and check if the problem has been resolved. Depending on your firewall software or hardware, you may need to lower the security level.
Also ensure to include Google Chrome in the allowed app list of the Windows 10 Defender.
Solution 6: Disable Multiple Internet Connections
Check whether you have multiple Internet connections running. Try to disable unnecessary connections and leave your primary connection active. Sometimes, this will fix the problem.
Solution 7: Disable Web or Ad Filtering Software
Disable the web filtering software, if you have one. If it’s confirmed that the software is causing err_name_not_resolved error, change its settings to make it less restrictive. If you can’t, you may need to uninstall it and find an alternative.
Solution 8: Other Solutions
Most of the time, those four solutions above are enough to resolve err_name_not_resolved error. Try the following solutions if none of these errors can be resolved:
- You need to make sure that the problem isn’t caused by external factors. Restart your computer into safe mode with network and make sure that you still have internet or network connection.
- Contact your internet service provider and confirm they do not block the site.
- Another way is to try connecting with other networks. If you are using a laptop, try to connect with the nearest Wi-Fi hotspot that is using a different network.
- Ensure your Chrome browser is using the latest version or reset the browser to factory settings.
- Try accessing the page in incognito mode which will disable the extensions. This will help if the extensions are causing the problem.
- The error can also happen due to the fact that the website is really not accessible. This is possible if the site owner changed the DNS or nameservers recently. So you can get the contact information from the cached page and inform the site owner that the page is not accessible due to DNS error. You may need to wait for few days for the DNS changes to propagate completely.