“DNS server is not responding” is not a browser error. It comes from your operating system’s own network troubleshooter — usually Windows Network Diagnostics — after it asked your configured DNS server for an address and got silence back.
That wording is more precise than it looks, and it is also frequently misleading. The troubleshooter is reporting what it observed, not diagnosing why. Your DNS server may be fine; something between you and it may be dropping the conversation.
Key Takeaway:
Your connection is almost certainly working. Only name lookups are failing. For most people the fix is one change — stop using the DNS server your router handed you, and set a public one directly on the device.
Confirm It Really Is DNS
Two commands separate a DNS fault from a dead connection. Open Command Prompt on Windows, or Terminal on macOS and Linux:
ping 8.8.8.8— contacts an address directly, no name lookup involvedping google.com— requires a name lookup first
| ping 8.8.8.8 | ping google.com | What it means |
|---|---|---|
| ✅ Works | ❌ Fails | Classic DNS failure — this guide applies |
| ❌ Fails | ❌ Fails | Your connection is down; DNS is a symptom |
| ✅ Works | ✅ Works | DNS recovered — the troubleshooter is reporting a past failure |
If the second row matches your result, stop here and work through Wi-Fi connected but no internet instead — you have a connectivity problem, not a name resolution one.
Why Your Router Is Usually the Culprit
Unless you have changed it, your device does not talk to your ISP’s DNS server directly. It talks to your router, which runs a small DNS forwarder and passes requests upstream. That forwarder is the weakest link in the chain: it runs on modest hardware, it holds its own cache, and it can stop responding while the router continues to pass ordinary traffic perfectly well.
This is why the error so often appears with a working internet connection, and why the two fixes below — restarting the router, or bypassing it for DNS entirely — resolve the large majority of cases.
The Fixes, in Order
1. Power-cycle the router properly
Unplug it at the wall, wait thirty seconds so its memory clears, then plug it back in and give it two minutes to come up. A reboot from the admin panel is not always equivalent — some models do not clear the DNS forwarder that way.
2. Set a public DNS server on the device
This is the fix that works when nothing else does, because it takes the router’s forwarder out of the path completely.
Windows: Settings → Network & Internet → your connection → Edit DNS server assignment → Manual → toggle IPv4 on → Preferred 1.1.1.1, Alternate 1.0.0.1. macOS: System Settings → Network → your connection → Details → DNS → add the same two addresses and remove any greyed-out entries.
Cloudflare (1.1.1.1) and Google (8.8.8.8) are the usual choices. Full instructions for phones, tablets and routers are in how to check and change your DNS settings.
3. Flush the cache and renew your lease
From an administrator Command Prompt on Windows, run these in order:
ipconfig /flushdnsipconfig /releaseipconfig /renew
This clears stored records and asks the router for fresh network configuration. Platform-specific commands are covered in how to flush your DNS cache.
4. Disable IPv6 temporarily
A genuinely common cause that most guides skip. If your network advertises IPv6 but the IPv6 path to your DNS server is broken, your device may keep trying it and time out before falling back. On Windows: Control Panel → Network and Sharing Centre → Change adapter settings → right-click your adapter → Properties → untick Internet Protocol Version 6.
Treat this as a diagnostic rather than a permanent fix. If it resolves the error, the real problem is your router’s IPv6 configuration or your ISP’s rollout — see what IPv6 is and whether you should use it. Re-enable it once the underlying issue is sorted.
5. Pause security software’s web filtering
Antivirus suites with network protection intercept DNS queries to filter them. When that component misbehaves — often after an update — queries vanish silently, which looks exactly like an unresponsive server. Disable the web-protection module specifically, retest, then re-enable it. If that was the cause, reinstall or update the suite rather than leaving protection off.
6. Check for DNS settings left behind by a VPN
VPN clients set custom DNS servers while connected. An unclean disconnect or an uninstall can leave those entries in place, pointing at a tunnel that no longer exists. Look at your adapter’s DNS configuration — if it lists an address you do not recognise, that is very likely the fault. Set it back to automatic or to a public resolver.
7. Reset the network stack
If the error survives everything above and affects only this machine, reset Windows’ networking configuration from an administrator Command Prompt:
netsh winsock resetnetsh int ip resetnetsh interface ipv4 reset
Restart afterwards. This rebuilds configuration that ordinary reboots leave untouched, and clears damage left by uninstalled network software.
🔍 If Every Device on the Network Fails
When phones, laptops and TVs all show name resolution failures at once, the fault is upstream of any single device — your router or your ISP’s resolver.
The decisive test: set a public DNS server on one device, as in step 2. If that device starts working while the others stay broken, your router’s forwarder or your ISP’s resolver is the problem. Fix it properly by setting the public resolver in the router’s DHCP settings, so every device on the network inherits it — that also removes your ISP’s ability to log every domain you look up, which is worth knowing about in its own right: what your ISP’s DNS server can see.
If you would rather not hand your lookups to Cloudflare or Google either, encrypting them is the alternative — see DNS over HTTPS explained, or route DNS through a VPN tunnel. If you go the VPN route, verify it is not leaking lookups back to your ISP with our free DNS leak test.
Frequently Asked Questions
Why does it say my DNS server isn’t responding when the internet works?
Because connectivity and name resolution are separate. Data can flow perfectly while the specific service that turns names into addresses is unreachable. That is exactly what the message describes.
Is it safe to use Google or Cloudflare DNS?
Technically yes, and both are more reliable than most ISP resolvers. The trade-off is that you move your query history from your ISP to that provider. Cloudflare’s 1.1.1.1 commits to not logging identifiable queries; if that trade matters to you, encrypted DNS or a VPN is the better answer.
Should I leave IPv6 disabled?
No. Use it as a test only. Leaving IPv6 off can break other services and is a workaround for a router or ISP problem that should be fixed properly.
Why did this start suddenly with no changes?
The usual causes are an ISP resolver outage, a router firmware update, or a security-software update that changed how DNS is filtered. Router power-cycle plus a manual public DNS server covers all three.
Does this error mean I’ve been hacked?
Almost never. It is far more often a wedged router or a filtering conflict. That said, if your DNS settings list a server you did not configure and did not come from a VPN, change it and update your router’s admin password.
Why does it only affect one computer?
Device-specific causes: local security software, a leftover VPN DNS entry, or a corrupted network stack. Steps 5 to 7 target exactly those.
Will resetting the network stack lose my Wi-Fi passwords?
It can clear saved networks and custom adapter settings, so have your Wi-Fi password available before running it. Your files are unaffected.