DNS Server not responding is an error message that appears while running the network connections troubleshooter. The DNS errors prevent users from connecting to websites on the internet as DNS converts Domain names into IP addresses. The internet should work fine on other devices if you face this error. Otherwise, the problem could be from the Internet Service Provider (ISP).
When this dns issue occurs, that simply means either the DNS is not supported by your internet connection, web browsers or the DNS servers are down. We have listed some important causes of this issue below that you can check to solve the problem.
- Corrupted DNS Cache- In many cases, the corrupted or damaged DNS server cache often produces this error. Therefore, to fix this, you will need to flush your DNS.
- DNS Server Down- There is a possibility that your DNS server is having issues, and due to that reason, the error is occurring. To avoid this, simply change the DNS to another or use the default one.
- Having Unsupported DNS- The leading cause of this issue is using an unsupported DNS. If your DNS is unsupported, change the DNS to automatic or manual to fix this error.
Before we move on to fixes, you must restart your router and ensure all the network equipment is working fine. You can test this by connecting your phone to the WiFi and checking your connection to the internet.
1. Change Public DNS
This DNS server not found error can be easily fixed by changing the current DNS to another, such as Google DNS, Cloudflare, and others. However, in my case, the error occurs due to a manual DNS. So when I changed it to automatic, the error was immediately resolved.
Some users have reported fixing this error using an alternate DNS server like Google’s. However, changing it to automatic might fix this error if you are already using a Google DNS or other DNS. Follow the steps:
- To change the DNS to manual or automatic, type the Control Panel from Start Menu
- Open the control panel and navigate to the following path
Control Panel\Network and Internet\Network and Sharing Center
- Click on your connection type such as Ethernet or WI FI
- Then, click Properties and select Internet Protocol Version 4 (TCP/IPv4)
- Then, click Properties
- For the manual DNS settings, select Use The Following DNS Server Addresses
- Type the DNS address you want to integrate. We Prefer Google DNS as it is fast compared to others
- For the Default DNS, select Obtain DNS Server Address Manually and click OK
- Once done, check if the error is fixed.
2. Power Cycle Your Router
If changing the DNS does not fix this error, power cycling the router might help as it temporarily disconnects all the connected devices, which sometimes fixes various issues. As per the affected users, power cycling the router helps to fix DNS server not responding error. Follow the steps to power cycle the WIFI router:
- Unplug the router’s charger from the electric outlet
- Wait for 2 to 3 minutes, then plug the charger back
- Wair for the router to turn on properly, then check if the error is resolved.
3. Flush DNS
The error will likely appear if you have an invalid or outdated DNS address. Hence to fix this, flush your DNS cache by following the below steps:
- Click Start Menu and type command prompt
- Right-click on it to run the terminal as an administrator
- Paste the following command in the terminal and hit Enter
ipconfig /flushdns ipconfig /registerdns
- Once done, check if the error is fixed.
4. Reset Winsock
If the error occurs due to incorrect or corrupted entries to the Winsock catalog, resetting the configuration to default along with registry values might fix this error. Winsock tells the computer how internet applications like browsers and others can access internet services. Therefore, try resetting the Winsock. Below are the steps:-
- Launch a command prompt by typing it from the Start Menu
- Open it as administrator and paste the following command, and press Enter
NETSH winsock reset catalog
5. Reset IPv4 and IPv6
The error can either be produced by the IPv4 or IPv6. To ensure there is no problem with the Internet Protocol version, we recommend resetting IPv4 and IPv6 as they can produce this error.
- Launch command prompt as administrator, then paste the following commands one by one to reset Internet Protocol Versions.
NETSH int ipv4 reset reset.log NETSH int ipv6 reset reset.log
6. Reset IP Address
If the issue is still there, try reassigning the new IP address, as we have almost applied everything except this one. Below are the steps:
- Open the command prompt and paste the following command to reset the IP address
ipconfig /release ipconfig /renew
7. Reset Network Settings
So far, we have tried everything to diagnose the source of the problem. However, If the error is not fixed after applying all methods above, you can try resetting network settings to fix this error. To do so:
- Click Start Menu and type settings
- Launch Setting and navigate to Network & Internet
- Scroll down to the bottom and click Network Reset
- Then, click Reset Now. This will restart your computer
- Once done, check if the issue is resolved.
If none of the methods shown above fixed this error, then it’s possible that this issue is occurring from your ISP’s end. If that’s the case, try contacting your ISP and let them know about this issue. You can also try connecting your computer through an ethernet cable as it is more stable, and it will automatically configure some network parameters in your Windows.
Moreover, you can try disabling your antivirus software temporarily as some of them use custom firewall rules using a modified DNS that can cause this issue.