Getting the Server DNS Address Could Not Be Found error in Google Chrome? Here is a helpful guide to help you resolve it!
DNS (or also known as Domain Name System) is used to match human-readable domain names with IP addresses, such as 188.8.131.52. This system makes sure you will visit the right place when entering a domain name in the web browser.
By default, your computer will use the default DNS server from your Internet Service Provider (ISP). However, this sometimes isn’t stable which could lead to many irritating issues, such as DNS Server Not Responding, DNS Lookup Failed, or DNS Probe Finished No Internet.
There are many third-party DNS server services you can use, like Google’s DNS, OpenDNS, or Level3. I’ve written an article that talks about a list of top 10 best DNS servers you should use. Check it out!
Don’t know how to change your DNS server on your computer, or your smartphone? Read this post to find out!
Fix Server DNS Address Could Not Be Found Error In Google Chrome
If there are any problems with your DNS server (such as it doesn’t respond or can’t be connected), it can’t match domain names with IP addresses correctly. Therefore, your web browser will show you a blank page, or an error page with an error message that you wouldn’t like to see.
In this article, I’m going to tell you a few methods that you can use to fix the “server DNS address could not be found” error on your Google Chrome browser.
1. Replace Your DNS Server With A Third-Party Provider
In most cases, there is a problem with your default DNS server from your ISP. Somehow, your computer can’t be connected or doesn’t respond so it can’t match your requested domain name to the right IP address. That’s the reason why you get this DNS error, as well as many other errors that are related to DNS.
Replacing your default DNS server with a third-party service like Google’s DNS or OpenDNS will help to load a website faster, more securely and especially more stable. By that, you will not encounter any DNS errors anymore.
The IP addresses of Google’s DNS are as follows:
The IP addresses of OpenDNS are as follows:
2. Flush DNS Cache And Reset IP Configuration
All DNS entries and IP addresses are stored in the cache of your computer so that the same queries can be run. If a website has changed its DNS entry or IP address lately, then you need to clean up all outdated entries. Otherwise, it will cause DNS errors, like I mentioned above, including this one.
Don’t know how to clear DNS cache and reset IP configuration? Here’s how to do it:
- Press Windows + X, then press A to open the Command Prompt program with administrator privilege.
- In the next step, perform all the following commands below, one by one:
- Then perform the these next commands:
netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log
You just need to restart your computer, and then everything will be back to normal.
3. Clear Host Cache In Google Chrome
Alongside the two methods above, you should also need to clear the host cache on your Google Chrome browser. It stores several items of data there, including hostnames, IP addresses, and expiry date.
To clean up this data, type:
in the address bar of your Google Chrome browser and press Enter.
After that, click on the “Clear host cache” button and restart your browser. This method also helped me to resolve issues related to DNS servers several times.
4. Restart DNS Client Service
In case you are still encountering the “server DNS address could not be found” issue, then restart DNS Client service in Windows Services can help to fix it.
To restart DNS Client service, press Windows + R, type: services.msc into the field and press Enter.
In the Windows Services application, locate DNS Client, right-click on it and select “Restart“.
After that, restart your Windows PC.
Still getting the Server DNS Address Could Not Be Found error when using Google Chrome? Drop your comment below so I can help you resolve it.