You type a website, hit Enter, and Windows throws back “DNS server not responding.” Your Wi-Fi icon still shows connected, yet nothing loads. The error means your PC could not translate a site name like google.com into the numeric IP address it needs, a job handled by DNS (the Domain Name System), which works like the internet’s phone book. Almost every time I see this, the cause is a stale cache, a router hiccup, or one wrong DNS setting — not a broken connection.
I have fixed this on dozens of friends’ laptops, and the same short sequence clears it nearly every time. Below is exactly what I run, in order, starting with the fastest move.
Quick Answer
To fix “DNS server not responding” on Windows, restart your router, then open Command Prompt as administrator and run ipconfig /flushdns. If the error stays, switch your DNS to Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1 / 1.0.0.1) in your adapter settings. Those three steps resolve most cases.
What causes “DNS server not responding”?
When you request a website, Windows asks a DNS server for that site’s IP address. If the lookup fails, you get this error. The usual culprits:
- Router crash or overload — your router needs a restart to clear its memory.
- Corrupted DNS cache — old or wrong records saved on your PC break the lookup.
- ISP’s DNS server is down — your provider’s servers are slow, overloaded, or offline.
- Outdated network adapter driver — the software running your Wi-Fi or Ethernet card has a bug.
- Antivirus or firewall blocking DNS — security software intercepts requests and blocks them by mistake.
- Corrupted TCP/IP stack — Windows’ core networking settings have gone wrong.
The error is almost always a small software glitch on your PC or router, not a dead connection.
How do I quickly restart the router and modem?
A router restart is the single most effective first step. It clears the router’s memory, drops stale connections, and pulls a fresh DNS assignment from your ISP. When every device in the house is affected — phones, tablets, laptops — this is almost certainly the fix. The first time it happened to me, this alone solved it before I touched a single Windows setting.
- Unplug your router (and modem, if it is a separate box) from the power outlet.
- Wait 30 seconds.
- Plug the modem back in first. Wait until its lights stabilize — about 60 seconds.
- Plug the router back in. Wait another 60 seconds.
- Try loading a website on the affected device.
Pro tip: Always unplug the power cable rather than pressing the router’s physical Reset button. The Reset button restores factory settings and wipes your custom Wi-Fi password — pulling the power does not.
Power-cycling the router fixes the majority of whole-house DNS errors in under three minutes.
How do I flush the DNS cache?
Windows saves DNS lookups in a local cache to speed up browsing, but that cache can go stale or corrupt. Flushing it forces Windows to fetch fresh records for every site. This is the step that bails me out most often on a single problem PC.
- Press Windows key + R, type
cmd, then press Ctrl + Shift + Enter to open Command Prompt as administrator. - Type this command and press Enter:
ipconfig /flushdns - You should see: “Successfully flushed the DNS Resolver Cache.”
- Restart your browser and test a website.
Troubleshooting tip: If you see “Access is denied,” you did not open Command Prompt as administrator. Close it, search for Command Prompt in the Start menu, right-click it, and choose Run as administrator.
Flushing the cache clears most single-device DNS failures without changing any settings.
Which DNS server should I switch to?
Your ISP’s DNS server may be down or just slow. Switching to a fast public resolver is one of the most reliable fixes, and it often speeds up browsing as a bonus. I keep Cloudflare set on my own machine for exactly this reason.
- Press Windows key + R, type
ncpa.cpl, and press Enter to open Network Connections. - Right-click your active connection (Wi-Fi or Ethernet) and select Properties.
- Click Internet Protocol Version 4 (TCP/IPv4), then click Properties.
- Select Use the following DNS server addresses and enter:
Preferred DNS server:8.8.8.8
Alternate DNS server:8.8.4.4 - Click OK, then Close. Open a browser and test.
Not sure which resolver to pick? Here are the three most popular free options and their addresses:
| Provider | Primary DNS | Secondary DNS |
|---|---|---|
| Google Public DNS | 8.8.8.8 | 8.8.4.4 |
| Cloudflare | 1.1.1.1 | 1.0.0.1 |
| OpenDNS | 208.67.222.222 | 208.67.220.220 |
Cloudflare’s 1.1.1.1 is consistently among the fastest resolvers worldwide and takes a privacy-first approach. If you want the full walkthrough for phones, Macs, and your router too, see my guide on how to change your DNS server on any device. You can confirm a public resolver is reachable on Cloudflare’s DNS status page.
A public resolver replaces a flaky ISP DNS and frequently makes pages load faster too.
What if the error still will not clear?
If the first three steps did not work, the problem sits deeper in Windows. Work through these in order.
Restart the DNS Client service
Windows runs a background DNS Client service that handles every lookup. If it froze, restarting it can clear the error on its own.
- Press Windows key + R, type
services.msc, and press Enter. - Scroll to DNS Client.
- Right-click it and select Restart.
- If Restart is greyed out, Windows is managing the service automatically — move on.
Reset the TCP/IP stack and Winsock
The TCP/IP stack and Winsock catalog are the core pieces Windows uses on any network. Corruption in either causes persistent DNS errors. Resetting them is safe and takes about two minutes.
- Open Command Prompt as administrator.
- Run each command, pressing Enter after each:
netsh winsock resetnetsh int ip resetipconfig /releaseipconfig /flushdnsipconfig /renew - Restart your computer once all commands finish.
Troubleshooting tip: If ipconfig /renew reports “media disconnected,” skip it — that is normal for Wi-Fi adapters in certain states and does not affect the reset.
Update or roll back the network adapter driver
An outdated or buggy driver can cause intermittent DNS failures. Updating usually fixes it, but if the error started right after a Windows update, rolling back is often the answer.
- Right-click the Start button and choose Device Manager.
- Expand Network Adapters.
- Right-click your Wi-Fi or Ethernet adapter and select Update driver → Search automatically for drivers.
- If the error followed a recent update, open the adapter’s Properties, go to the Driver tab, and click Roll Back Driver.
Temporarily disable antivirus or firewall
Some antivirus tools and third-party firewalls intercept DNS requests to scan them and can block them by accident. Disabling protection briefly is a safe test — just avoid untrusted sites while it is off.
- Right-click your antivirus icon in the system tray (bottom-right of the taskbar).
- Choose an option like Disable protection, Pause, or Turn off temporarily.
- Try loading a website. If it works, your security software is the culprit.
- Re-enable protection immediately after the test.
- Look for DNS filtering, “Web Shield,” or HTTPS scanning in its settings and add an exclusion, or ask the vendor’s support team.
These deeper resets clear the stubborn cases that survive a router restart and a cache flush.
Common Mistakes to Avoid
- Pressing the router’s physical Reset button instead of power-cycling it. That button restores factory settings and deletes your Wi-Fi password. Fix: unplug the power cable instead — same effect, no side effects.
- Skipping “Run as administrator” in Command Prompt. The
ipconfig /flushdnsandnetshcommands fail or error without admin rights. Fix: right-click Command Prompt and choose Run as administrator. - Forgetting to click OK when changing DNS. New servers do not apply until you click OK in both the TCP/IPv4 Properties and adapter Properties windows. Fix: click OK on every window, not Close.
- Testing in the same browser tab. Browsers cache their own DNS and page data. Fix: open a fresh private/incognito window to test.
- Leaving antivirus disabled after the test. An unprotected PC is a real risk. Fix: re-enable protection the moment the diagnostic is done.
Frequently Asked Questions
What does “DNS server not responding” mean?
It means your PC asked a DNS server to turn a website name into an IP address and got no reply, so the browser cannot load the page. For example, my laptop showed it once while the Wi-Fi icon stayed connected — the connection was fine, only the name lookup had stalled.
Why does this error only affect one device?
When other devices work fine, the problem lives on that one computer — usually a corrupted cache, a wrong DNS setting, or a driver bug. On my own machine, flushing the cache (above) and switching to Google’s DNS cleared it while every phone in the house stayed online.
Is it safe to use Google’s public DNS (8.8.8.8)?
Yes. Google’s 8.8.8.8 / 8.8.4.4 and Cloudflare’s 1.1.1.1 / 1.0.0.1 are free, reliable, and used by hundreds of millions of people. I have run Cloudflare as my default for over a year with zero issues and faster lookups than my ISP’s.
Will resetting TCP/IP delete my files or settings?
No. The TCP/IP and Winsock reset only restores Windows’ internal networking rules to default. When I ran it on a relative’s PC, every file, app, and saved Wi-Fi password stayed exactly as it was.
Can a VPN cause “DNS server not responding”?
Yes. VPNs route DNS through their own servers, and a failing one can trigger this error. I have seen a half-connected VPN cause it — disconnecting the VPN and testing directly fixed it instantly.
What if none of the fixes work?
Then the fault is likely with your ISP, so contact them for remote diagnostics. If your connection is slow rather than dead, my guide on how to fix slow internet covers speed-focused tweaks. When a friend’s error persisted past every step here, the ISP confirmed a regional DNS outage on their end.
Conclusion
The “DNS server not responding” error sounds technical, but it is almost always fixable in minutes. Restart the router, run ipconfig /flushdns, and switch to Google’s 8.8.8.8 — that clears the vast majority of cases. Work through the steps in order and test after each one.
If your Wi-Fi shows connected but nothing loads at all, read my guide on Wi-Fi connected but no internet. If your connection drops over and over, see Wi-Fi that keeps disconnecting next.