On Microsoft Windows PCs, Windows Network Diagnostics can be run to help diagnose internet connection problems. If you're not sure whether or not your computer is reporting DNS Server Not Responding errors, follow these steps: Select Start and then choose Settings. Select Network & Internet. Navigate to the DNS server and select the option that best mirrors your used internet protocol (IPv4 or IPv6). Enter the address of the DNS server you want to use in place of the current one. Google’s DNS server will be 18.104.22.168 in the preferred DNSv4 and 22.214.171.124 in the alternate DNS server. The DNS entries for these laptops are not being updated reliably, resulting in problems when our helpdesk has to support them, as they are unable to connect to them by DNS name. We are also in the process of configuring SCCM 2012, and it is causing issues with this as well. The idea of setting up a DNS can seem daunting. In this guide, we'll show you three methods to change the DNS settings on Windows 10 for more reliable and private resolvers. For Windows: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows 2019 Server, Windows 2016 Server, Windows 2012 Server, Windows 2008 Server, Windows Home Server, Windows 2003 Server (Service Pack 2) 512 MB RAM, 10 MB Free Hard Disk space for installed program, 20 MB or more recommended for local caching; For Mac: Mac OS X 10.10 Yosemite.
Suddenly you cannot access any websites through the Internet. Then you try to troubleshoot the network problems on your Windows. It tells you the DNS server not responding is the culprit. You may see one of these:
“The DNS server isn’t responding.
Your computer appears to be correctly configured, but the device or resource (DNS server) is not responding.”
Don’t worry if this problem occurs. You can fix this problem with our following guide.
If you’d like to know why you can’t browse the Internet due to the ‘DNS server not responding, you can go to read the reason part. Otherwise, follow along with the solutions directly.
Bonus Tip: Try using VPN to fix the connection problem.
Note: The screens shown below are from Windows 10, but all the methods also apply to Windows 7/8.
First, let’s figure out what a DNS server is. DNS (Domain Name System) server helps to translate the website address into the IP address for your browser to connect to.
For example, when you want to access our website: www.drivereasy.com on Chrome, the DNS server translates it into our public IP address: 126.96.36.199 for Chrome to connect to.
So you may know if there’s any wrong with your DNS server, you cannot access any website on your browser. No exception that if your DNS server stops responding, you cannot access the websites through the Internet.
The DNS server not responding error could be probably caused by an incorrect DNS server address. So you can follow these to correct your DNS server address:
1) On your keyboard, press the Windows logo key and R at the same time to invoke the Run box.
2) Type control and press Enter.
3) Click Network and Sharing Center in Large icons.
4) Click Change adapter settings.
5) Right-click on Local Area Connection, Ethernet or Wi-Fi according to your Windows. Then click Properties.
6) Click Internet Protocol Version 4(TCP/IPv4), then Properties.
7) Tick on Obtain an IP address automatically and Obtain DNS server address automatically. Then click OK.
8) Click Internet Protocol Version 6(TCP/IPv6), then Properties.
9) Tick on Obtain an IP address automatically and Obtain DNS server address automatically. Then click OK.
Restart your computer and try to access the website you want to go to again and see if it succeeds.
1) Type cmd in the search box from the Start menu. Then right-click on Command Prompt to select Run as administrator.
Note: Click Yes when prompted by the User Account Control.
2) On the open black window, type the following commands and press Enter after each.
Then restart your computer and try to access the website you want to visit again and see if it succeeds.
Your DNS server won’t respond if the network adapter driver is outdated. You can update your network adapter driver manually or, if you’re not confident playing around with drivers, you can do it automatically with Driver Easy.
Driver Easy will automatically recognize your system and find the correct drivers for it. You don’t need to know exactly what system your computer is running, you don’t need to risk downloading and installing the wrong driver, and you don’t need to worry about making a mistake when installing.
You can update your drivers automatically with either the FREE or the Pro version of Driver Easy. But with the Pro version it takes just 2 clicks (and you get full support and a 30-day money-back guarantee):
1) Downloadand install Driver Easy.
2) Run Driver Easy and click the Scan Now button. Driver Easy will then scan your computer and detect any problem drivers.
3) Click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system (this requires the Pro version – you’ll be prompted to upgrade when you click Update All).
Note: You can do it for free if you like, but it’s partly manual.
After updating your network adapter driver, please restart your computer. Try to access the website you want to go to again and see if it succeeds.
If your modem or router doesn’t work properly, the DNS server could stop responding, either. You can restart your modem and router if you have one to solve the problem.
1) Press the power button of your modem or router to power off, then wait for a while and press the power button again to start it again.
2) Try to access the website you want to go to again and see if it succeeds.
Hopefully, this article has helped you fixed the problem. Feel free to comment below with your own experiences and share with your friends or colleagues if they’re experiencing the same problem.-->
This article discusses how to troubleshoot issues from DNS clients.
Open a Command Prompt window as an administrator on the client computer.
Run the following command:
Verify that the client has a valid IP address, subnet mask, and default gateway for the network to which it is attached and being used.
Check the DNS servers that are listed in the output, and verify that the IP addresses listed are correct.
Check the connection-specific DNS suffix in the output and verify that it is correct.
If the client does not have a valid TCP/IP configuration, use one of the following methods:
For dynamically configured clients, use the
ipconfig /renew command to manually force the client to renew its IP address configuration with the DHCP server.
For statically configured clients, modify the client TCP/IP properties to use valid configuration settings or complete its DNS configuration for the network.
Verify that the client can contact a preferred (or alternate) DNS server by pinging the preferred DNS server by its IP address.
For example, if the client uses a preferred DNS server of 10.0.0.1, run this command at a command prompt:
If no configured DNS server responds to a direct pinging of its IP address, this indicates that the source of the problem is more likely network connectivity between the client and the DNS servers. If this is the case, follow basic TCP/IP network troubleshooting steps to fix the problem. Keep in mind that ICMP traffic must be allowed through the firewall in order for the ping command to work.
If the DNS client can ping the DNS server computer, try to use the following
nslookup commands to test whether the server can respond to DNS clients. Because nslookup doesn't use the client's DNS cache, name resolution will use the client's configured DNS server.
For example, if the client computer is named client1, run this command:
If a successful response is not returned, try to run the following command:
For example, if the FQDN is client1.corp.contoso.com, run this command:
You must include the trailing period when you run this test.
If Windows successfully finds the FQDN but cannot find the short name, check the DNS Suffix configuration on the DNS tab of the Advanced TCP/IP Settings of the NIC. For more information, see Configuring DNS Resolution.
For example, if the DNS server is named DC1, run this command:
If the previous tests were successful, this test should also be successful. If this test is not successful, verify the connectivity to the DNS server.
For example, if the failing record was app1.corp.contoso.com, run this command:
If all four of these tests were successful, run
ipconfig /displaydns and check the output for the name that failed. If you see 'Name does not exist' under the failing name, a negative response was returned from a DNS server and was cached on the client.
To resolve the issue, clear the cache by running
If name resolution is still failing, go to the Troubleshooting DNS Servers section.