Which 'DNS server' is Windows saying isn't responding — mine or the website's?

Yours. When the Windows troubleshooter reports 'DNS server not responding,' the server it means is the resolver your computer is configured to ask — almost always your home router, which forwards to your ISP's resolver. It is not the authoritative DNS server that actually owns a website's records. This is the single most useful thing to understand about the error, because it points the fix in the right direction: the problem is on the path between you and your resolver, not out at the website. That's why the same error hits every site at once rather than just one, and why switching to a different public resolver so often fixes it instantly — you've simply stopped asking the machine that wasn't answering.

If it's my resolver, why does the website look 'down' too?

Because your computer can't turn any name into an address until some resolver answers. DNS is the first step of loading a page — before your browser can connect to a server, it has to look up that server's IP, and that lookup goes to your configured resolver. If the resolver is silent, every name fails to resolve, so every site appears unreachable even though the sites themselves are fine and their own DNS is working perfectly for everyone else. 'The internet is down' and 'my one resolver stopped answering' produce identical symptoms from where you're sitting. The way to tell them apart is to ask a different resolver and see if the problem moves.

Is changing to 8.8.8.8 or 1.1.1.1 a real fix or just a workaround?

It's both, and which one depends on what you find afterward. If pointing Windows at a public resolver like Cloudflare's 1.1.1.1 or Google's 8.8.8.8 makes the problem vanish, you've proven the fault was in the resolver you were using before — your router's or ISP's — and the public resolver is a legitimate permanent fix. If the error persists even against a known-good public resolver, DNS isn't really your problem; something local is blocking the queries from leaving at all — a firewall, a VPN client, security software intercepting DNS, or a broken network adapter — and that's what to fix next. So the switch is also a diagnostic: it tells you which side of your own machine the fault is on.

DNS Server Not Responding (Windows): Fix

What This Error Actually Means

Windows tells you “DNS server not responding,” and the natural reading is that some server out on the internet has failed. It almost never has. The “DNS server” in that message is your resolver — the machine your computer is configured to ask when it needs to turn a name like example.com into an IP address. On a home network that’s your router, which passes the question along to your ISP’s resolver. When Windows says it isn’t responding, it’s saying: I asked the resolver you gave me, and I got silence.

That one fact reorganizes the whole problem. The website you were trying to reach has its own DNS servers, run by whoever owns the domain, and they’re almost certainly fine — answering questions for everyone else on earth right now. Your machine just can’t get its question answered by the one resolver it’s pointed at. The fix isn’t out there. It’s on the short path between your computer and your resolver.

Resolver vs. Authoritative: The Distinction That Solves It

There are two very different kinds of “DNS server,” and confusing them is why this error sends people down the wrong path.

Your resolver (recursive DNS) is the errand-runner. You ask it a question; it goes and finds the answer, caches it, and hands it back. You have exactly one or two of these configured, and they’re usually your router or your ISP. This is what Windows is complaining about.
The authoritative server is the source of truth. It holds the actual records for one specific domain and answers only questions about that domain. There are millions of them, one set per domain, and you never talk to them directly — your resolver does.

“DNS server not responding” is a resolver problem by definition. If it were an authoritative-server problem, exactly one website would fail while everything else worked — and Windows wouldn’t phrase it as a blanket connectivity failure. When everything stops resolving at once, suspect the errand-runner, not the source.

The Fastest Test: Ask a Different Resolver

Before touching anything else, do the one test that isolates the fault in about thirty seconds: point Windows at a public resolver and see if the problem moves.

Open Settings → Network & Internet, go to your active adapter’s properties, edit the DNS assignment to Manual, turn on IPv4, and set:

Cloudflare: 1.1.1.1 and 1.0.0.1
Google: 8.8.8.8 and 8.8.4.4
Quad9: 9.9.9.9

Save, then reload a page.

The error vanishes → your old resolver (router or ISP) was the thing that wasn’t answering. The public resolver is a fine permanent choice, and you’ve found your culprit.
The error persists → DNS isn’t really the problem. Your queries aren’t reaching any resolver, which points at something local: a VPN, a firewall, security software intercepting DNS, or the adapter itself. Move to the next section.

This is faster and more informative than any amount of restarting, because it tells you which side of your own machine the fault is on.

Clearing the Local State

If a resolver swap didn’t fix it — or before you commit to changing your DNS — reset the local pieces that go stale. Open Command Prompt or PowerShell as administrator and run, in order:

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset

flushdns empties Windows’ DNS cache, so a bad or expired cached answer can’t keep haunting you.
release/renew gets a fresh lease from your router, including the DNS server it hands out over DHCP.
netsh winsock reset rebuilds the network socket configuration, which clears the damage left behind by uninstalled VPNs and security tools. Reboot after this one — it doesn’t fully take effect until you do.

If the router itself is the wobbly resolver, the oldest fix in the book still earns its reputation: power-cycle it. Pull the plug, wait thirty seconds, plug it back in, and let it fully come up before testing.

Diagnose with DechoNet

DNS Check resolves a name from DechoNet’s own servers, completely independent of your machine and your ISP. If a domain resolves cleanly here but not on your PC, the records are healthy and the fault is entirely local — exactly the confirmation you need before spending time on your own network.
DNS Propagation Check queries the same name across many public resolvers worldwide at once. If they all agree on an answer, the domain’s authoritative DNS is fine everywhere but your resolver — which is the whole point of “DNS server not responding.”

Verification Checklist

Confirm the scope: does every site fail, or just one? Every site points at your resolver; a single site points at that domain’s records, which is a different problem entirely.
Swap to a public resolver (1.1.1.1, 8.8.8.8) and retest — this both fixes and diagnoses.
Run ipconfig /flushdns, then release/renew.
Run netsh winsock reset and reboot.
Temporarily disable any VPN client and third-party security suite, then retest — both commonly intercept DNS.
Power-cycle the router if the fault followed your old (router/ISP) resolver.
Confirm from the outside: check the domain on DechoNet. Resolving there but not locally proves the problem is on your side.

When It’s Not Your Resolver

If a public resolver still returns “not responding,” DNS has been ruled out — the queries aren’t getting out. Look at what sits between Windows and the network: a VPN or proxy that’s up but broken, security software in “protect my DNS” mode that’s silently dropping queries, a driver problem on the network adapter, or an upstream outage where your connection has no working path at all. And if the trouble is genuinely limited to one website while everything else resolves, that’s not this error — that’s a problem with that domain’s own DNS, and the check tools above will show it to you directly.

Check your own domain now

Free, no sign-up. Runs the exact check this guide describes and shows what to fix.