Table of Contents
Google Chrome is one of the most popular web browsers. However, it does not mean that it operates properly. Recently many Chrome users reported about “Server DNS address could not be found” error which prevents from normal browsing sessions. Typically, the error is a result of some issues with DNS misconfiguration. However, other reasons might be responsible for preventing accessing specific websites or web pages with Google Chrome.
“Server DNS address could not be found” error can be solved quite easily by:
- clearing host cache;
- configure DNS settings;
- renewing and flushing DNS;
- restarting DNS client service.
We have explained all the methods that should help to get rid of the error below. But first, we want to explain the error and discuss reasons why it occurred.
The meaning of “Server DNS address could not be found” Chrome error
As we have mentioned at the beginning, the error shows up on the screen when something goes wrong with DNS settings or server. The problem mostly bothers Windows 8, Windows 8.1 and Windows 10 users. However, on the rare occasions, macOS users can encounter the same problem as well.
Reasons for the error
According to the researchers, the “Server DNS address could not be found” Google Chrome error is typically triggered if:
- the domain is unresponsive;
- the DNS server cannot be accessed;
- IP address has been changed at a server-level.
Simply speaking, the error shows up on the screen when the DNS server of the website cannot retrieve the IP address of your desired website.
However, on some rare occasions, the error can be caused by browser extension or add-ons.
Symptoms of the Chrome error
Visually, this Google Chrome error barely differs from the others. When some of the above-mentioned issues occur, you receive the gray window that informs:
“Server DNS address could not be found”
The error also suggests a couple of methods to get rid of the problem, such as:
- reloading website
- checking Internet connection;
- Checking proxy, firewall, and DNS configuration.
Differently than other similar Chrome errors, “Server DNS address could not be found” may not block access to all websites you want to access. The error indicates the problem with a particular domain or web page.
Therefore, you might be able to waste your time on Facebook, but be unable to access BBC or other popular news portals or social networks.
According to Chrome users’ experiences shared on various support and help forums, some people noticed that this particular error crashed or corrupted Chrome add-ons and extensions. In this case, people receive a notification when they try to open and use the extension that their Wi-Fi connection is not established successfully.
Four methods to fix “Server DNS address could not be found” error on Google Chrome
Typical solutions to get rid of Chrome errors include restarting the browser or computer, updating Chrome, restating Wi-Fi router. However, these simple and obvious solutions are not helpful in this case. As you already know, the source of the program are issues with DNS configuration. You can find and try the following solutions.
Method 1. Clear host cache
Deleting host cache helps to get rid of “Server DNS address could not be found” error if the problem is related to browser extensions or plugins:
- Open Google Chrome in Incognito mode by pressing three vertical dots at the top right of the page and choosing the New incognito window.
- In the URL bar, enter chrome://net-internals/#dns and click Enter.
- Find and click the Clear Host Cache button.
- Then run Command Prompt by right-clicking Windows key and choosing Command Prompt (Admin) from the list.
- Then copy and paste the following commands and click Enter after each one:
netsh int ip reset
netsh winsock reset
- Close Command Prompt and restart Google Chrome to check if the problem still exists.
Method 2. Configure DNS settings
Misconfigured DNS settings is the most common source of the “Server DNS address could not be found” error on Google Chrome. Follow the steps below to configure them correctly:
- In the Windows search box type Control Panel.
- Open it from the search results and navigate to Network and Sharing Center.
- Click Change adapter settings and right-click on the connection icon (Local Area Connection or Wireless Network Connection).
- Open Properties.
- Put the tick on next to Internet Protocol Version 4 (TCP /IPv4) option.
- Navigate to Properties again.
- This time open the General tab.
- Select Obtain DNS server address automatically option and then hit OK.
- If Obtain DNS server address automatically option has been already selected, choose Use the following DNS server address instead option.
- Enter one of the following server addresses:
Preferred DNS server: 18.104.22.168
Alternate DNS server: 22.214.171.124OR
Preferred DNS server: 126.96.36.199
Alternate DNS server: 188.8.131.52
- Click OK.
Restart the browser and check if this method helped to get rid of Chrome error.
Method 3. Renew and flush DNS settings
If none of the two techniques helped to solve the problem with “Server DNS address could not be found” error, try renewing and flushing DNS settings:
- Right-click Windows key and choose Command Prompt (Admin) from the list.
- In the Command Prompt type the following commands and press Enter after each of them:
netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log
Method 4. Restart DNS client service
The last method that should help to solve this Google Chrome error suggests restarting DNS client service:
- Open Run dialog box by right-clicking Windows start button and choosing it from the list.
- Enter services.msc and click OK.
- Look up for DNS Client.
- Once you find it, right-click it and choose Restart option.
The summary of the error
“Server DNS address could not be found” error is a common problem for Windows users. However, on the rare occasions, it might show up on Mac computers. However, just like many similar Google Chrome errors, this one can be fixed by solving all issues related to DNS.
If none of the explained methods helped to fix the error, you should consider reinstalling the browser or checking a computer for potentially unwanted programs (PUP) or viruses.