LiveChat 
Support 
DNS Server Not Responding? How to Isolate the Cause and Fix It
You clicked a link, waited, and your browser handed you a flat verdict: “DNS server not responding.” Nothing loaded. No page, no error from the website itself, just a quiet failure that feels like the whole internet shrugged at you.
The good news is that this error is one of the most fixable problems you will ever meet. It is rarely the website’s fault, and it almost never requires a technician. It requires a calm, ordered approach: change one thing, test, and watch what happens. That is how you isolate the cause instead of guessing at it.
Let me walk you through exactly what the message means, who is actually responsible (usually your side, not the site), and the precise sequence of fixes that resolves it for the overwhelming majority of people.
Key Takeaways
• “DNS server not responding” means the resolver you are using did not answer when your device asked it to translate a domain name into an IP address. The website is not the immediate problem; the lookup is.
• The cause is usually on your side: your router, your network adapter, or your ISP’s DNS server, not the site you are trying to reach.
• The single highest-success fix is to switch to a reliable public DNS resolver such as `8.8.8.8` (Google) or `1.1.1.1` (Cloudflare). Do this before you touch drivers or safe mode.
• Work in order: restart the router, isolate with a second device, change the resolver, flush the cache, reset the adapter, then disable VPN or firewall.
• “Server IP address could not be found” is the same family of error and responds to the same fixes.
What does “DNS server not responding” actually mean?
Every time you visit a website, your device performs a quiet translation. You type a human name like `darazhost.com`, but computers route traffic using numeric IP addresses. The Domain Name System (DNS) is the directory that converts one into the other, and the machine that does the converting for you is called a resolver.
When you see DNS server not responding, your device sent a question to that resolver, asking for the IP address behind a name, and waited. No answer came back in time. The connection between you and the directory broke down before the website was ever contacted.
This is the crucial distinction: the website is not refusing you. The directory you are using to find the website never replied. That is why the error points at a *server* (the DNS server) rather than the page. Related messages like “server IP address could not be found” and “DNS server unavailable” describe the same breakdown from a slightly different angle: your device could not complete the name-to-address lookup. (If you want the foundational picture of how this directory works, see our explainer on ).
Is the problem you or the website?
This is the first thing to settle, and there is a fast way to settle it. In the large majority of cases, the problem is on your side, your device, your router, or your internet provider’s DNS, not the website.
Here is the quick test. Try to open two or three different, unrelated websites. If *every* site fails with a DNS error, the fault is almost certainly local: your resolver is down or unreachable for everything. If only *one* site fails while others load normally, that points toward a problem with that specific domain’s hosting or its authoritative DNS records, a different situation entirely.
You can confirm the “it’s the site” case from another angle: pull up the same site on your phone using mobile data instead of Wi-Fi. If it loads on mobile data but fails on your home network, the issue lives somewhere between your device and your ISP. If it fails everywhere, the site itself may have a problem worth reporting to its owner.
For this article, we are focused on the common case: the lookup is failing on your side. Let’s isolate and fix it.
What causes the DNS server not responding error?
A handful of culprits account for nearly every instance. Knowing them helps you predict which fix will land:
- A router or modem glitch. Routers run small operating systems and, like any computer, they hang. A stale or crashed DNS service on the router is probably the single most common cause.
- A wrong or dead DNS server set. Your device or router may be pointed at a DNS server that no longer responds, perhaps one that was entered manually long ago and has since gone offline.
- Your ISP’s DNS is down. Internet providers run their own resolvers, and they have outages. When the ISP resolver stumbles, every device on your connection sees the error at once.
- A network adapter issue. The Wi-Fi or Ethernet adapter on your computer can fall into a bad state, holding a stale configuration that no longer works.
- Firewall or antivirus interference. Security software sometimes blocks DNS traffic (port 53) after an update or a misconfiguration, silently breaking lookups.
- A VPN. VPN clients reroute your DNS through their own servers. If the VPN’s resolver is flaky or the client disconnects badly, your lookups fail.
Here is the insight that saves the most time: “DNS server not responding” almost always points at the resolver you are using, not the website you want to reach. Because of that, the single highest-success fix is simply to switch your device or router to a reliable public DNS resolver like `8.8.8.8` or `1.1.1.1`. Most real-world cases are a flaky or misconfigured ISP or router DNS, and changing the resolver sidesteps the entire problem in one move. So before you reset adapters, update drivers, or boot into safe mode, change the resolver and re-test. You will resolve a surprising share of these errors right there and skip the rest of the checklist entirely.
How do you fix DNS server not responding, step by step?
Work through these in order. The point of ordering them is to isolate the cause: each step either fixes the problem or rules out a category, so you are never guessing. Stop as soon as your sites load.
1. Restart your router and modem
Power-cycle the hardware first because it is the most common fix and costs nothing.
- Unplug both your modem and your router from power.
- Wait a full 60 seconds so the devices fully discharge and clear their state.
- Plug the modem back in first and let it fully come online (steady lights).
- Plug the router back in and wait for it to reconnect.
- Re-test a website.
2. Try a second device to isolate the fault
Open the same sites on a different device on the same network, a phone, a tablet, another laptop.
- If the second device works, the problem is isolated to your first device (its adapter, drivers, VPN, or security software). Skip ahead to the device-level fixes below.
- If every device fails, the problem is the router or the ISP DNS. The resolver change in the next step is your best move.
3. Change your DNS to a public resolver
This is the highest-value fix. You are replacing whatever resolver is failing with a fast, reliable public one.
On Windows:
- Open Settings → Network & Internet → Change adapter options (or run `ncpa.cpl`).
- Right-click your active connection and choose Properties.
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
- Choose Use the following DNS server addresses and enter:
“`text Preferred DNS server: 8.8.8.8 Alternate DNS server: 8.8.4.4 “`
Prefer Cloudflare? Use `1.1.1.1` and `1.0.0.1` instead. Click OK, then re-test.
On macOS: open System Settings → Network → (your connection) → Details → DNS, then add `8.8.8.8` and `1.1.1.1` to the list and apply.
For a wider, more permanent fix, set these same numbers in your router’s DNS settings so every device on the network benefits. (Full walkthrough here: ).
4. Flush your DNS cache
Your device stores past lookups to speed things up. When those stored entries go stale, they cause errors. Clearing the cache forces fresh lookups.
Windows (Command Prompt as administrator):
“`bat ipconfig /flushdns “`
macOS (Terminal):
“`bash sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder “`
You should see a confirmation that the cache was flushed. Re-test. (More detail and platform variations: ).
5. Reset your network adapter
Release and renew your network configuration to clear a stuck adapter state. In an administrator Command Prompt on Windows:
“`bat ipconfig /release ipconfig /renew “`
If that does not help, reset the deeper networking stack:
“`bat netsh winsock reset netsh int ip reset “`
Restart your computer after the `reset` commands for them to take full effect.
6. Temporarily disable your VPN, firewall, or antivirus
If a VPN is running, disconnect it and re-test, its resolver may be the one that is failing. Then temporarily disable third-party firewall or antivirus software and try again. If disabling security software fixes it, re-enable the software and create an exception rather than leaving yourself unprotected; the fix is to correct the rule, not to run without protection.
7. Update your network drivers
An outdated or corrupted network adapter driver can cause persistent lookup failures. On Windows, open Device Manager → Network adapters, right-click your adapter, and choose Update driver. Where possible, download the latest driver directly from the adapter or laptop manufacturer.
8. Test in safe mode with networking
As a final isolation step, boot into Safe Mode with Networking. Safe mode loads only essential drivers and services. If DNS works there but not normally, a third-party program, often security software or a network utility, is the culprit, and you can disable startup items one by one to find it.
Cause and fix at a glance
| Likely cause | The fix that targets it |
|---|---|
| Router or modem hung | Power-cycle the router and modem (Step 1) |
| Wrong or dead DNS server set | Change to a public resolver `8.8.8.8` / `1.1.1.1` (Step 3) |
| ISP DNS server down | Change to a public resolver, or wait out the outage (Step 3) |
| Stale DNS cache | Flush the cache with `ipconfig /flushdns` (Step 4) |
| Stuck network adapter | Release/renew, then reset the stack (Step 5) |
| VPN rerouting DNS badly | Disconnect the VPN and re-test (Step 6) |
| Firewall or antivirus blocking port 53 | Temporarily disable, then add an exception (Step 6) |
| Outdated adapter driver | Update the network driver (Step 7) |
| Background software interfering | Test in Safe Mode with Networking (Step 8) |
If, after the resolver change and a cache flush, a *single* site still fails while everything else works, you are likely looking at a problem on the site’s side, often a misconfigured record that produces an rather than a “not responding” timeout.
How DarazHost keeps the answering side reliable
Everything above addresses the side *you* control as a visitor. But every DNS lookup has a second half: the authoritative server that actually holds a domain’s records and answers the query. If that side is slow or unreliable, even a perfectly configured visitor sees errors.
DarazHost runs fast, reliable, redundant DNS for the domains you host with us, so the authoritative side always answers, no single point of failure, low-latency responses, and records that resolve cleanly worldwide. And if you *own* a website and visitors are reporting DNS errors, our 24/7 support team helps you confirm your nameservers and DNS records are healthy so the problem is found and fixed quickly rather than left to guesswork.
If you want to understand the full path a request travels, from a visitor’s resolver to your authoritative server, our complete guide to networking and DNS for hosting lays out the whole journey.
Frequently asked questions
Does “DNS server not responding” mean the website is down? Usually not. The error means the resolver you queried did not answer, so the lookup failed before the website was ever contacted. If other sites load fine and only one fails, that points toward the site; if every site fails, the problem is your resolver, router, or ISP.
Is “server IP address could not be found” the same problem? It is in the same family. Both messages describe a failed name-to-IP lookup. The same fixes apply: change to a public DNS resolver, flush your cache, and restart your router. The wording differs by browser, but the underlying breakdown is the same.
Which public DNS server should I use, 8.8.8.8 or 1.1.1.1? Both are excellent, free, and fast. `8.8.8.8` is Google’s resolver; `1.1.1.1` is Cloudflare’s. Either will resolve most “DNS server not responding” cases. If one does not help, try the other, since it is a two-minute change.
Why does the error keep coming back after I fix it? A recurring error usually means the underlying cause was not addressed, only its symptom. If a power-cycle fixes it temporarily but it returns, set a public resolver permanently in your router so the flaky ISP DNS is no longer in the path. Persistent recurrence on one device often points to an outdated network driver or interfering security software.
Can a VPN cause this error? Yes. VPN clients route your DNS queries through their own servers, and if that server is unreachable or the client disconnects badly, every lookup fails. Disconnect the VPN and re-test; if that resolves it, switch the VPN’s DNS settings or contact the VPN provider.
