Fix "DNS Server Not Responding" in Windows 10/11
Your PC can't talk to the DNS server. Nine times out of ten it's a stale cache or bad adapter settings. Let's fix it fast.
Yeah, that “DNS Server Not Responding” error is annoying. You’re in the middle of something and suddenly nothing loads. I’ve seen this hundreds of times. Here’s how to kill it fast.
Step 1: Flush the DNS Cache and Reset the Network Stack
Open Command Prompt as Administrator. Click Start, type cmd, right-click it, and pick “Run as administrator.” Then run these commands in order:
ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew
netsh winsock reset
netsh int ip reset
Don’t skip any. Each one does something different. After the last command, restart your PC. This clears any corrupted cache, resets your IP lease, and rebuilds the network driver stack. It works for about 60% of DNS issues.
Step 2: Change Your DNS Server (When Step 1 Fails)
If flushing didn’t help, your ISP’s DNS is probably the problem. They’re often slow or flaky. Switch to Google DNS or Cloudflare DNS.
- Open Control Panel > Network and Sharing Center > Change adapter settings.
- Right-click your active connection (Wi-Fi or Ethernet) > Properties.
- Select “Internet Protocol Version 4 (TCP/IPv4)” > Properties.
- Choose “Use the following DNS server addresses” and enter:
Preferred: 8.8.8.8
Alternate: 8.8.4.4
For Cloudflare, use 1.1.1.1 and 1.0.0.1. Click OK and restart your browser. This bypasses your ISP’s DNS entirely. I use Cloudflare on all my machines — it’s faster and more reliable.
Why Did This Happen?
DNS stands for Domain Name System. It translates website names (like google.com) into IP addresses. When your computer can’t reach the DNS server, it can’t resolve any domain names. The culprit is almost always one of three things:
- A corrupt DNS cache from a bad network session or a faulty VPN disconnect.
- Your ISP’s DNS server having an outage or being overloaded.
- A misconfigured network adapter — often after a Windows update or driver change.
Flushing the cache clears the garbage. Changing DNS servers removes the ISP variable. Resetting Winsock fixes the stack if Windows itself corrupted it.
Less Common Variations of This Issue
DNS Server Not Responding on One Device Only
If other devices on your network work fine, check your antivirus or firewall. Some security software (looking at you, Norton and McAfee) hijack DNS settings. Temporarily disable them. If it works, reinstall the firewall component.
DNS Error After a VPN Disconnect
VPNs often change your DNS settings and don’t revert them. Run the commands from Step 1 again. If that doesn’t fix it, go to Control Panel > Network and Sharing Center > Change adapter settings. Right-click your VPN adapter > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties. Check “Obtain DNS server address automatically.” Then disable and re-enable the adapter.
DNS Probe Finished No Internet in Chrome
Chrome throws this error when its internal DNS resolver is broken. Steps above usually fix it. One extra trick: type chrome://net-internals/#dns in the address bar and click “Clear host cache.” That’s Chrome’s own DNS cache.
Prevention Tips
- Use a static DNS server — set Google or Cloudflare DNS in your router’s settings. That way every device on your network uses it. Instructions vary by router model, but it’s usually under WAN or Internet settings.
- Keep Windows updated — Microsoft patches DNS stack vulnerabilities. Don’t skip updates.
- Reboot your router once a month — routers can accumulate bad DNS cache too. Unplug it for 30 seconds.
- Disable IPv6 if you don’t need it — some ISPs have flaky IPv6 DNS. In adapter properties, uncheck “Internet Protocol Version 6 (TCP/IPv6).” Test if it helps. Re-enable it if your ISP requires it.
If you’ve tried all this and still get the error, it’s probably a hardware issue — bad Ethernet cable, failing router, or a driver problem. Try a different cable or USB Wi-Fi adapter. I’ve seen a faulty cable cause more DNS errors than most people think.
Was this solution helpful?