“DNS Server Not Responding” is one of the most common error messages in home networking, and it’s also one of the most misunderstood. This error specifically means your device can’t translate website names into the numerical addresses computers actually use to find them, even though your underlying internet connection might be working perfectly fine. Here’s how to fix it.
What DNS Actually Does
Every website has a numerical IP address, but humans use names instead, like example.com. DNS, the Domain Name System, is the service that translates those names into addresses behind the scenes every time you visit a site. When DNS fails, your internet connection can be completely healthy while every website still refuses to load, because your device simply doesn’t know where to find them anymore.
Step 1: Restart Your Router and Modem
As with most networking issues, start simple. Unplug your modem and router, wait 30 seconds, plug the modem back in first, wait two minutes, then plug the router back in. This resolves temporary DNS server hiccups more often than you’d expect.
Step 2: Try a Different Browser
Occasionally this error is specific to one particular browser rather than your actual network. Open a different browser entirely and try loading a website. If it works fine there, the issue is isolated to your original browser’s settings or cache rather than a true DNS problem.
Step 3: Switch to a Public DNS Server
Your internet provider’s default DNS servers can occasionally experience outages or slowdowns of their own, completely separate from your actual internet connection. Switching to a reliable public DNS service often resolves this instantly. Popular free options include Google DNS (8.8.8.8 and 8.8.4.4) and Cloudflare DNS (1.1.1.1 and 1.0.0.1). You can change this either on your router, which applies to every device on your network, or on an individual device’s network settings.
Step 4: Flush Your DNS Cache
Your device stores recently used DNS results locally to speed up future visits, but this cache can become corrupted. On Windows, open Command Prompt as an administrator and type “ipconfig /flushdns”. On a Mac, open Terminal and type “sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder”. This clears out any bad cached entries causing the error.
Step 5: Disable Secondary Network Connections
If you have a VPN, virtual network adapter, or even certain antivirus software with network filtering features active, these can interfere with normal DNS resolution. Temporarily disable any VPN connections and see if the error disappears, which confirms whether the VPN’s own DNS handling is the source of the problem.
Step 6: Update Your Network Adapter Driver
An outdated network driver can cause DNS-related errors even when every other part of your network setup is correct. On Windows, check Device Manager for driver updates under Network Adapters. Keeping this updated resolves a surprising number of persistent DNS errors that seem to defy every other fix.
Step 7: Disable IPv6 Temporarily
Some home networks have inconsistent IPv6 support between the router and the internet provider, which can cause DNS resolution conflicts. As a diagnostic test, try disabling IPv6 on your specific device’s network adapter settings and see if the error resolves. If it does, you can leave IPv6 disabled or investigate your router’s IPv6 configuration further.
Step 8: Restart in Safe Mode With Networking (Windows)
If you suspect a specific piece of software, like a VPN client or security tool, is causing persistent DNS conflicts, restarting your computer in Safe Mode with Networking loads only essential drivers and services. If the error disappears in Safe Mode, you’ve confirmed a specific installed program is the culprit, and can work on identifying which one through process of elimination.
Step 9: Reset the Router’s DNS Settings
If you previously configured custom DNS settings on your router and have since forgotten the details, incorrect or outdated entries can cause this exact error for everyone on the network. Log into your router’s admin panel, check the DNS settings, and either correct them or set them to “Automatic” to use your provider’s default servers, or manually enter the public DNS addresses from Step 3.
Final Thoughts
DNS Server Not Responding is rarely about your actual internet connection being down; it’s about the translation service that makes website names usable failing somewhere along the way. Switching to a reliable public DNS service, combined with flushing your local cache, resolves this error in the overwhelming majority of cases within just a few minutes.