Few Internet errors are more frustrating than “DNS server not responding.” Your Wi-Fi may still look connected and everything seems normal, yet websites suddenly refuse to open.
Fortunately, the cause is often simple. A router restart, fresh DNS cache, or different DNS resolver may be all you need. When those quick fixes do not work, the pattern of the problem usually tells you where to look next.
What Does “DNS Server Not Responding” Mean?
DNS connects domain names with the IP addresses computers use to reach websites and other online services. When you enter a domain into your browser, your device normally asks a DNS resolver for the information it needs.
If the resolver does not answer, the request times out, or something prevents your device from reaching it, the browser may report that the DNS server is not responding.
That does not automatically mean the DNS server itself is down. The real problem could be your router, Wi-Fi connection, network settings, VPN, firewall, or Internet provider.
Start With the Quick Fixes
Before changing advanced network settings, start with the boring fixes. They are boring because they work surprisingly often.
Try opening a few different websites first. If only one domain fails, the problem may belong to that website rather than your connection. You can also try another browser or another device connected to the same network.
If the problem affects everything, restart your router. Turn it off, wait around 30 seconds, and turn it back on. Restart your computer or phone as well so both sides of the connection get a clean start.
A mobile hotspot is another useful test. If the same device works normally through mobile data but not through your Wi-Fi, you have already narrowed the problem down considerably.
Is It Really a DNS Problem?
The fastest way to troubleshoot this error is to look at what is affected.
| What is happening? | Where to look first |
|---|---|
| Only one website fails | The domain or its DNS configuration |
| Every website fails on one device | Device or local DNS settings |
| Every device on the network fails | Router, resolver, or ISP |
| Wi-Fi fails but mobile data works | Local network |
| Everything works after disabling VPN | VPN or its DNS configuration |
| DNS queries work but websites still fail | The problem may not be DNS |
This simple distinction can save a lot of unnecessary troubleshooting.
If five devices stop working at the same time, there is little reason to start changing DNS settings individually on every laptop.
Clear the DNS Cache
Your computer keeps recently used DNS answers in a local cache. This makes browsing faster because the same information does not need to be requested repeatedly.
Occasionally, however, an old or incorrect cached entry causes trouble. How long DNS information remains cached is controlled partly by its DNS TTL, or Time to Live.
On Windows, you can clear the local DNS cache by opening Command Prompt and running:
ipconfig /flushdns
Once the cache is cleared, try the website again. Your device will need to request fresh DNS information rather than relying on previously stored answers.
Try a Different DNS Resolver
Most people never choose their DNS resolver. Their router or Internet provider does it automatically, and normally there is no reason to think about it.
But resolvers can experience outages, routing problems, or heavy load just like any other Internet service. If your current resolver is not responding, trying another one is a useful test.
If websites immediately begin working after the change, the original DNS resolver was probably involved. You can configure a different resolver on a single device for testing or change it on the router if you want the whole network to use it.
If switching resolvers makes no difference, the problem is likely somewhere else.
Check Your DNS Settings
Custom DNS settings can be useful, but they are also an easy place for old configurations to hide.
Open your network settings and check whether DNS addresses are being assigned automatically or have been entered manually. A typo, outdated server address, or configuration left behind by old software can stop DNS resolution completely.
If you are unsure why custom addresses are there, temporarily switching back to automatic DNS configuration can help. If everything starts working again, you have found a good place to investigate further.
Your Router Might Be the Real Problem
When every device connected to the same network starts complaining about DNS, the router deserves attention.
Many routers receive DNS information from the ISP and then pass DNS requests between local devices and an upstream resolver. If that process gets stuck, the problem can appear on phones, laptops, televisions, and anything else using the network.
Restarting the router is the obvious first step. If the problem returns, check which DNS servers the router is configured to use.
A useful rule to remember is:
One device broken? Look at the device. Several devices broken? Look at the network.
It is not a perfect rule, but it is a very good starting point.
VPNs and Proxies Can Interfere With DNS
VPN software changes the route your Internet traffic takes, and DNS traffic may be sent through the VPN as well.
That means a VPN connection problem can sometimes appear as a DNS problem. Disconnect the VPN temporarily and try loading the website again. The same test can be useful if you use a proxy.
If everything starts working without the VPN, check its DNS settings, reconnect to another VPN server, or investigate whether the provider is experiencing an issue.
You do not necessarily need to stop using the VPN. You have simply found the part of the connection that deserves attention.
Check the Firewall Without Leaving It Disabled
Firewalls and security applications occasionally block legitimate DNS traffic because of an incorrect or overly strict rule.
This is especially worth checking if the problem started after installing new security software or changing firewall settings. A temporary test can tell you whether the application is involved.
If disabling the software makes DNS work again, do not leave it disabled. Find the rule causing the problem and correct it.
Trading a DNS error for an unprotected computer is not much of an upgrade.
Use Nslookup or Dig to See What DNS Is Doing
At some point, guessing becomes less useful than simply asking DNS what is happening.
The NSlookup command can show whether a DNS server is returning an answer for a domain. For example:
nslookup example.com
If you receive an address, DNS is responding. If the query repeatedly times out, the resolver or the route to it may be having problems.
For a more detailed look, the Dig command shows information such as the response code, DNS server, query time, and returned records.
These tools become particularly useful when comparing resolvers. If one answers immediately and another does not respond at all, the mystery suddenly becomes much smaller.
When Only One Website Will Not Open
If nearly every website works normally except one, stop troubleshooting your entire network for a moment.
The problem may belong to the domain itself. Its A or AAAA record could be wrong, its name server delegation may be broken, or a CNAME may point somewhere it should not.
Recent DNS changes can also cause different users to receive different answers for a while because of caching and DNS propagation.
Testing the domain with another resolver is useful here. If the same domain fails from several networks and resolvers while other domains work normally, the evidence starts pointing away from your computer and toward the domain’s DNS configuration.
DNSSEC Can Turn a Configuration Error Into a Failed Lookup
DNSSEC adds cryptographic validation to DNS so resolvers can check that certain DNS information is authentic.
Normally, users never notice this happening. A broken configuration is a different story.
An incorrect DS record, missing signature, or other problem in the validation chain may cause validating resolvers to reject the DNS response. From the user’s perspective, the website can simply appear unavailable.
If a domain stops resolving shortly after DNSSEC changes, checking the configuration should be high on the list. Our DNSSEC breakdown explains how the protection works in more detail.
Sometimes the DNS Server Really Is Overloaded
Not every DNS error comes from a badly behaved laptop.
DNS servers can become overloaded because of infrastructure problems, unexpected traffic, or attacks. A DNS flood, for example, attempts to overwhelm DNS infrastructure with large volumes of requests.
When a resolver or authoritative server is under too much load, queries may respond slowly or time out entirely.
For the user, the symptom can be deceptively ordinary: websites hesitate, DNS requests fail, and refreshing the browser sometimes works and sometimes does not.
This is one reason reliable DNS infrastructure uses redundancy and multiple server locations instead of depending on a single machine.
Wi-Fi Problems Can Look Like DNS Problems
DNS queries still need a functioning network to reach their destination.
Weak Wi-Fi, packet loss, interference, or an unstable router can interrupt those queries. The browser eventually reports a DNS problem because DNS was the step that failed, even though the underlying cause was the wireless connection.
Try reconnecting to Wi-Fi, moving closer to the router, or using Ethernet if it is available. Testing through a mobile hotspot is particularly useful because it changes the network without changing the device.
If DNS works perfectly on another connection, there is little reason to start editing the domain’s DNS records.
Fixing “DNS Server Not Responding” on Windows
Windows users can troubleshoot the problem in a fairly simple order:
- Restart the router and computer.
- Try several websites and another browser.
- Run
ipconfig /flushdns. - Check the DNS addresses configured on the network adapter.
- Run
nslookup example.com. - Try another DNS resolver.
- Disconnect VPN or proxy software temporarily.
- Check firewall and security settings.
There is a reason to keep the steps in roughly this order. Start with changes that are easy to reverse and avoid rebuilding network settings before you know they are actually the problem.
When Should You Contact Your Internet Provider?
If every device on the network has the same problem and local troubleshooting gets you nowhere, the ISP may be involved.
Internet providers often operate DNS resolvers for their customers. An outage or routing problem on their side can leave you connected to the Internet while DNS requests fail.
Signs that the problem may be outside your network include several devices failing at once, your ISP’s resolver not answering, and mobile Internet working while your home or office connection does not.
At that point, checking the provider’s service status or contacting support makes more sense than repeatedly restarting the laptop.
How Website Owners Can Reduce DNS Problems
For website owners, the problem looks a little different. You cannot control a visitor’s Wi-Fi, but you can make your own DNS infrastructure less fragile.
Using more than one authoritative DNS server is a basic starting point. Monitoring is equally important because a DNS problem that nobody notices is free to become a much larger one.
For services where availability matters, DNS Failover can help direct users toward an alternative endpoint when the primary service becomes unavailable.
A reliable Managed DNS provider can also provide distributed infrastructure and reduce the burden of operating DNS servers independently.
The goal is not to create a system that can never fail. The Internet has a sense of humor about promises like that. The goal is to avoid one small failure taking everything else down with it.
A Quick Way to Find the Problem
If you remember only one part of this guide, make it this:
- One website is broken: investigate the domain.
- One device is broken: investigate the device.
- Every device is broken: investigate the router, resolver, or ISP.
- Everything breaks only with a VPN: investigate the VPN.
- DNS answers correctly but the site still fails: start looking beyond DNS.
This will not diagnose every possible problem, but it usually tells you where to begin.
Frequently Asked Questions About DNS Server Not Responding
Q1: Why Is My DNS Server Not Responding? – Common causes include a temporary resolver problem, incorrect DNS settings, router issues, stale DNS cache, VPN software, firewall rules, or a wider Internet connection problem.
Q2: What Is the Fastest Way to Fix a DNS Server Not Responding? – Restart the router and device first. If that does not work, clear the DNS cache and test another DNS resolver.
Q3: Can My Router Cause a DNS Error? – Yes. If the router cannot forward DNS requests correctly, several devices connected to it may experience DNS problems at the same time.
Q4: Will Changing DNS Servers Fix the Problem? – It can if the current resolver is unavailable, overloaded, or having routing problems. It will not fix an unrelated Wi-Fi problem or incorrect DNS records on the affected domain.
Q5: Can a VPN Cause DNS Problems? – Yes. VPNs may use different DNS servers or change how queries are routed. A VPN connection or configuration problem can therefore stop DNS resolution from working correctly.
Q6: Why Does Only One Domain Fail to Resolve? – The domain may have incorrect DNS records, name server problems, cached old information, or a DNSSEC configuration error.
Q7: How Can I Check Whether a DNS Server Is Working? – Commands such as nslookup and dig can send DNS queries directly and show whether the resolver returns an answer.
Q8: Is “DNS Server Not Responding” Always a DNS Problem? – No. Weak Wi-Fi, packet loss, router problems, firewalls, VPNs, or a wider Internet outage can create similar symptoms.
Conclusion
The DNS server not responding error looks more complicated than it usually is. Start with the simple checks, then work out whether the problem affects one website, one device, or the whole network.
Hi, I’m Bella, a technology enthusiast who enjoys making complex tech topics clear, practical, and easy to understand. Outside of writing, I love trail running, biking, traveling, and photography.