DNS Server Not Responding: How to Fix It (Windows, Mac, Linux)

You try to open a website and instead of the page you get a blank screen and a message: “DNS server not responding.” (You might also see “Your DNS server might be unavailable” or “The DNS server isn’t responding” — they all mean the same thing.) It sounds serious, but in the vast majority of cases the fix is quick and lives on your side — your device, your router, or your ISP’s resolver — not the website.

This guide walks through every proven fix in order, from the 30-second quick wins to the deeper solutions, for Windows, macOS, and Linux — plus how to tell in under a minute whether the problem is yours or something further out.

What “DNS server not responding” means

Every time you visit a site, your device asks a DNS server to translate the domain name (like copahost.com) into an IP address. The “not responding” error means your device sent that request and got no reply in time — so the browser has no IP to connect to, and shows the error instead of the page. (For the fundamentals, see what DNS is and how it works.)

The key thing to understand: this error sits at the boundary between your device, your local network, your router, and your ISP — so the culprit can be anywhere along that chain. The good news is that the chain is short, and you can test each link quickly.

Unlike DNS_PROBE_FINISHED_NXDOMAIN (where the domain doesn’t exist), DNS_PROBE_STARTED (where the lookup can’t complete), or ERR_CONNECTION_TIMED_OUT (where the server didn’t answer), “DNS server not responding” specifically means the resolver itself isn’t answering.

First: is it your device, your network, or your ISP?

Before changing settings, spend 30 seconds narrowing down where the problem is — it tells you which fix to apply:

• Try another website. If only one site fails but others load, it’s not your DNS server — it’s that specific site. If every site fails, your resolver is the suspect.
• Try another device on the same network. If your phone also fails on the same Wi-Fi, the problem is the router or ISP (not your computer). If only one device fails, it’s that device.
• Try mobile data. Load the site on your phone over cellular (not Wi-Fi). If it works there but not on Wi-Fi, the problem is your home network or ISP.
• Try another browser. If it works in a different browser, the issue is browser-level (cache/settings), not the DNS server.

That quick triage points you straight to the right section below.

How to fix “DNS server not responding”

Work through these in order — quickest and most common first.

1. Restart your router and modem

The single most effective fix. Routers keep their own DNS state, and it can go stale or crash. Unplug the router (and modem) from power, wait a full 30 seconds, then plug them back in and let them fully reconnect. This is a power cycle, not a factory reset — nothing gets wiped. A huge share of “not responding” errors clear here.

2. Flush your DNS cache

A corrupted local cache can make lookups fail. Clearing it forces fresh resolution. Full per-platform guide: how to flush DNS. The essentials:

3. Switch to a public DNS server

If your ISP’s resolver is down or unreliable — a very common cause — pointing your device at a public resolver fixes it immediately, and often speeds up browsing too. Use Cloudflare (1.1.1.1 / 1.0.0.1) or Google (8.8.8.8 / 8.8.4.4). Full step-by-step for every platform is in our guide to the best DNS servers and how to change them. The short version:

• Windows: Settings → Network & Internet → your connection → DNS server assignment → Edit → Manual → enter the addresses.
• macOS: System Settings → Network → your connection → Details → DNS → + → add the addresses.
• Linux: Network settings → IPv4 → DNS from Automatic to Manual, or nmcli on the command line.

Switching resolvers is also a great diagnostic: if a public DNS fixes it instantly, your ISP’s resolver was the problem.

4. Try a different browser or clear its cache

If the triage pointed to the browser, update it to the latest version or try another (Chrome, Firefox, Edge, Safari). Also clear Chrome’s separate DNS cache at chrome://net-internals/#dns → Clear host cache.

5. Disable secondary network connections and VPN

Unused adapters, a VPN, or a second active connection can route DNS the wrong way. Temporarily disconnect your VPN and disable secondary network adapters (Ethernet if you’re on Wi-Fi, virtual adapters), then reload.

6. Temporarily disable antivirus / firewall

Security software can block DNS queries. Turn off your firewall or antivirus briefly to test — if the page loads, re-enable it and adjust its settings (allow the “DNS Client” service) rather than leaving protection off. To confirm it’s software, boot into Safe Mode with Networking; if DNS works there, a third-party app is the culprit.

7. Disable IPv6 (if your network doesn’t support it well)

The IPv4→IPv6 transition can trip up DNS on networks or ISPs with incomplete IPv6 support. Disabling IPv6 on the adapter is a common fix:

• Windows: Network Connections (ncpa.cpl) → right-click your adapter → Properties → uncheck Internet Protocol Version 6 (TCP/IPv6) → OK.
• macOS: System Settings → Network → your connection → Details → TCP/IP → Configure IPv6 → Link-local only (or Off).

8. Update your network adapter driver (Windows)

An outdated or corrupted network driver can cause DNS failures. In Device Manager → Network adapters → right-click your adapter → Update driver. Restart and test.

9. Reset the network stack

If nothing above works, reset the network configuration to defaults:

On Windows you can also use Settings → Network & Internet → Advanced network settings → Network reset. On macOS, creating a new network location (System Settings → Network → Locations) gives you a clean network config.

Is it ever the website’s fault?

Usually not — but occasionally. If you run a site and visitors report “DNS server not responding” when trying to reach it (and it fails from every network, not just yours), the problem is on the domain’s side: misconfigured or missing DNS records, wrong nameservers after a migration, or an authoritative DNS outage at your host. Check that your domain’s nameservers and A records are correct, and allow for DNS propagation after any change. A host with reliable, well-configured DNS prevents this from reaching your visitors in the first place.

Frequently asked questions

What does “DNS server not responding” mean?
It means your device sent a request to translate a domain name into an IP address, and the DNS server didn’t reply in time. Without that translation, your browser has no address to connect to, so it shows the error instead of the page. The cause is usually local — your router, device, or ISP’s resolver.

How do I fix “DNS server not responding”?
Start with the three quick fixes: restart your router (power off 30 seconds), flush your DNS cache, and switch to a public DNS like Cloudflare (1.1.1.1) or Google (8.8.8.8). If those don’t work, try another browser, disable VPN and secondary adapters, temporarily disable your firewall, and — on some networks — disable IPv6.

Is “DNS server not responding” my fault or the website’s?
Almost always it’s on your side — your device, router, or ISP’s DNS server — which is why local fixes resolve most cases. It’s rarely the website, unless you own the site and its DNS records or nameservers are misconfigured, in which case every visitor sees it.

Why does my DNS server keep not responding?
Recurring errors usually point to an unreliable ISP resolver, a failing router, or a conflict from security software or IPv6. Switching to a stable public DNS (Cloudflare or Google) on your router fixes the most common recurring cause — a flaky ISP resolver — for every device at once.

Does flushing DNS fix “DNS server not responding”?
It can, when the cause is a corrupted local cache. Flushing forces fresh lookups and is a quick, safe first step. If the resolver itself is down, though, you’ll also need to switch to a public DNS — flushing alone won’t help if the server isn’t answering.

Why do I get “DNS server not responding” on my console or smart TV?
The same causes apply to game consoles (PlayStation, Xbox) and smart TVs — they rely on the same router and DNS as your other devices. The most reliable fix is to set a public DNS (like 8.8.8.8) directly in the device’s network settings, or on your router so every device benefits at once. Restarting the router first often clears it.

Conclusion

“DNS server not responding” looks alarming but is usually one of the quickest web errors to fix — and almost always on your side. Start with the big three: restart your router, flush your DNS cache, and switch to a public DNS like Cloudflare (1.1.1.1) or Google (8.8.8.8). If those don’t clear it, work down through browser, VPN, firewall, IPv6, and a network reset. The triage at the top — another site, another device, mobile data — tells you where to look before you change a thing. And if every device on your network fails no matter what, it’s likely your ISP’s resolver: switching to a public DNS is both the fix and the proof.