Whether you’re using Google Chrome on Windows or on Android smartphone, you can anytime get an error saying ERR_NAME_NOT_RESOLVED. This error, in general, occurs when the domain name cannot be resolved and this is why the website cannot be opened.
Google Chrome is one of the fastest, reliable and easy-to-use web browsers that is compatible with many devices and operating systems. Even being compatible with multiple devices, you must have seen this error numerous times while browsing through Chrome. This error appears due to DNS resolution problem.
What is ERR_NAME_NOT_RESOLVED?
The error: ERR_NAME_NOT_RESOLVED can appear anytime on your browser, restricting you to access various websites. Not only this, there are many other similar errors that can create a restriction for you to browse a website of your choice. These similar but different errors are inclusive of: Err_name_not_resolved WiFi, Err_name_not_resolved DNS, Err_name_not_resolved Internet Explorer, Err_name_not_resolved TP link etc.
So, let us first know the fixes for ERR_NAME_NOT_RESOLVED in Chrome.
How to Fix ERR_NAME_NOT_RESOLVED in Google Chrome?
Out of numerous ways, here we have compiled a list of the best ways that can help you resolve this error in easy steps. Let’s have a look:
1. Clear Browsing Data
The first thing is clear browsing data. It consists of a record of web pages you have visited in the past. This includes the name of the websites along with the URL, cookies, caches and whatnot. This entire data is stored in your browser and can restrict you to access websites causing ERR_NAME_NOT_RESOLVED error. For those who do not know how to clear browsing data in Chrome, follow the steps below:
- Open Google Chrome.
- On the top-right corner, click on three dots icon to access ‘More tools’.
- Under ‘More tools’, locate ‘Clear browsing data’.
From the window that opens, select the data you wish to remove from the cache. Ensure you do not miss to select remove ‘cookies and other site data’ from the list. Once selected, click on ‘clear data’ and restart Chrome to see if you still receive ERR_NAME_NOT_RESOLVED error.
2. Clear Chrome Host Cache
Apart from just deleting Chrome browsing data, you can also try clearing the Google Chrome host cache. For this, open Google Chrome and a new Incognito window. In the address bar, type in ‘chrome://net-internals/#dns’, and press Enter. Now, locate ‘clear host cache’ button and click over it. There are probable chances of this way to fix ERR_NAME_NOT_RESOLVED error in Chrome.
3. Change Your DNS
DNS is referred to Domain Name System and it allows a user to access websites easily. But, what if your ISP’s DNS is not working? This is the time you need to change it. The process to change DNS is simple, and to resolve error ERR_NAME_NOT_RESOLVED by changing DNS, follow the steps below:
- On your Taskbar locate Network icon. Right-click on it, and select your network.
- Click on the network name and a window will open.
- In the Window that opens, click on ‘Change adapter options’.
- Now, right-click on your network connection, and choose properties.
- Under properties tab, select Internet Protocol Version 4 (TCP?IPv4).
- Click Properties. Now, select ‘Use the following DNS server addresses’ and enter ‘126.96.36.199’ as Preferred DNS server and ‘188.8.131.52’ as Alternate DNS server.
- After you enter the changed values, click OK to save DNS settings.
4. Check Your Antivirus
Even Antivirus programs can lead to ERR_NAME_NOT_RESOLVED error. This error can easily be fixed by checking your antivirus settings and disabling a few of the essential features. If even after disabling features, you can’t access the website, then try uninstalling the entire antivirus program. We believe that removing antivirus entirely will help. You can reinstall the antivirus software on your computer to ensure protection for your PC, once done with the website.
Does It Help?
We hope all the ways listed above can help you fix Google Chrome error ERR_NAME_NOT_RESOLVED. We’re listening! Let us know whether it helped you or not? If you know any other fixes for this error, let us know in the comments section below.
For more tech updates, follow Systweak Blogs.