Fix 'DNS Server Not Responding' on Windows 10 & 11

30-Second Fix: Run the Network Troubleshooter

You're reading this because the Wi-Fi icon has a yellow triangle, or you get that dreaded "DNS Server Not Responding" error in the browser. Before you dive into anything complicated, try the built-in Windows troubleshooter. It's not a magic bullet, but I've seen it fix things like a stuck DNS cache in seconds.

1. Right-click the network icon in the system tray (bottom-right).
2. Select Troubleshoot problems.
3. Windows runs a check. If it finds something, click Apply this fix.
4. Restart your browser. If it works, you're done. If not, move on.

This fixes maybe 1 in 10 cases. The rest need a real kick in the pants.

5-Minute Fix: Flush DNS and Reset the Stack

The most common reason for a DNS error is a corrupted or outdated DNS cache on your machine. Windows holds onto old IP addresses and when they change, your PC gets confused. Here's how to clear that out.

1. Press Windows Key + R, type cmd, then press Ctrl+Shift+Enter to run as Administrator.
2. In the black window, type these commands one at a time, pressing Enter after each:

ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew
netsh winsock reset
netsh int ip reset

3. After all commands run, type exit and close the window.
4. Restart your PC.

This has saved me more times than I can count. Had a client last month whose entire print queue died because of a stuck DNS cache — same fix worked for his network shares. If your internet comes back, you're golden. If not, keep reading.

15-Minute Fix: Change Your DNS Server Manually

Your ISP's DNS servers are often slow, flaky, or just plain broken. I've seen ISPs go down for hours while Google or Cloudflare stay rock solid. You're not locked into what your ISP gives you. Let's switch.

For Ethernet or Wi-Fi (the reliable way)

1. Press Windows Key + R, type ncpa.cpl, and hit Enter.
2. Right-click your active connection (Wi-Fi or Ethernet) and choose Properties.
3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
4. Check Use the following DNS server addresses.
5. Enter these values (pick one set):

6. Click OK on both windows.
7. Go back to the command prompt and run ipconfig /flushdns again.
8. Restart your browser and test.

I use Cloudflare personally — it's faster than Google for most stuff, and they don't track you. If you're still stuck after this, your issue isn't DNS. It could be a bad router, a dying network card, or your ISP having a bad day. Try a different device on the same network. If that works, it's your PC. If not, reboot your router by unplugging it for 30 seconds.

One more thing: if you're using a VPN, disconnect it. VPNs often override your DNS settings and can cause this exact error. Had a guy last week whose VPN client was pointing to a dead DNS server. Turned it off, problem solved.

That's the whole playbook. Start with the flushes, switch DNS if needed, and reboot. You'll be back online in under 15 minutes. If none of this works, it might be time to check your router's firmware or call your ISP — but 9 times out of 10, the manual DNS fix does it.