Fix 'DNS Server Not Responding' in 5 Minutes

It's maddening when your browser says 'DNS server not responding' but your phone connects fine. I've seen this hundreds of times. The fix is almost always the same, so let's skip the runaround.

The Quick Fix

You're going to flush your DNS cache and switch your computer to use Google's public DNS. This overrides your router's flaky DNS settings.

Open Command Prompt as Administrator.
Hit the Windows key, type cmd, right-click 'Command Prompt' and pick 'Run as administrator'. Click Yes when Windows asks.
Flush the DNS cache.
Type this and press Enter:
```
ipconfig /flushdns
```
You should see 'Successfully flushed the DNS Resolver Cache'. If not, you didn't run as admin. Close and try again.
Release and renew your IP (optional but good).
Type these commands one at a time, pressing Enter after each:
```
ipconfig /release
ipconfig /renew
```
The second command might take 10-15 seconds. You'll see your IP address pop up. If you get an error, don't worry, move on.
Set Google DNS manually.
Go to Control Panel > Network and Sharing Center > Change adapter settings (on the left).
Right-click your active connection—either 'Ethernet' or 'Wi-Fi'—and pick Properties.
Find 'Internet Protocol Version 4 (TCP/IPv4)' in the list, select it, and click Properties.
In the bottom half, pick 'Use the following DNS server addresses'. Fill in:
```
Preferred DNS server: 8.8.8.8
Alternate DNS server: 8.8.4.4
```
Click OK, then Close.
After clicking OK you should see the window close. Your connection will flicker for a second. Quick test: open a browser and try loading any site.

What to expect after the fix: Pages should load immediately. If they don't, restart your browser or hit Ctrl+F5 to force a fresh page load.

Why This Works

Your ISP's DNS server is often slow or straight-up broken. Google's DNS (8.8.8.8) is fast and reliable. Flushing DNS clears any bad cached entries that Windows keeps around. Together, they bypass the broken DNS your router hands out.

The real trigger for this error? It's almost always your router's DHCP handing out a bad DNS server. Maybe your ISP had a glitch, or your router is old and its firmware is buggy. I've seen this on Netgear R7000s, TP-Link Archer C7s, and even ISP-provided gateways. Changing it at the PC level sidesteps the whole mess.

Less Common Variations

Still broken? Turn off IPv6 DNS

Some routers mess with IPv6 DNS. Go back to that IPv4 properties window, scroll down to 'Internet Protocol Version 6 (TCP/IPv6)', uncheck it, and click OK. Test again.

Windows 11 Secure DNS gotchas

Windows 11 has a 'Secure DNS' toggle that can override your manual settings. Go to Settings > Network & internet > Wi-Fi (or Ethernet) > Hardware properties. Look for 'DNS server assignment'—click Edit. Switch from Automatic to Manual, turn IPv4 on, and enter 8.8.8.8 and 8.8.4.4 again. Make sure 'Secure DNS' under that is set to 'Off' or 'Unencrypted only'. I've seen Secure DNS on Windows 11 cause this exact error because it fights with router settings.

Third-party antivirus or VPN interference

If you have Norton, McAfee, or a VPN like NordVPN, they sometimes shove their own DNS in. Temporarily disable the antivirus or VPN. Then flush DNS again (ipconfig /flushdns). If the error goes away, you need to configure that app to use Google DNS too—look in its settings under 'Network' or 'DNS'.

Corrupted DNS cache deeper than flush

Rare, but sometimes the cache is corrupt at the registry level. Only do this if the normal flush didn't work. Open Command Prompt as admin and run:

net stop dnscache
net start dnscache

Then flush again. This restarts the DNS Client service entirely.

How to Stop This From Happening Again

Set Google DNS directly on your router. That way every device in your house gets fast DNS. To do that, log into your router's admin page (usually 192.168.1.1 or 192.168.0.1), look for 'Internet' or 'WAN' settings, and change the DNS fields to 8.8.8.8 and 8.8.4.4. Save and reboot the router. Now your PC can go back to automatic DNS, and you won't see this error again.

Also, keep your router firmware updated. Old firmware on a 5-year-old Linksys WRT1900AC is a common cause. Check the manufacturer's support site for a firmware file, and apply it via the router's admin panel.

One more thing—if you're on Windows 11, turn off the 'Secure DNS' toggle in settings permanently. It's buggy and rarely helps. You don't need it with Google DNS, which supports DNS over HTTPS anyway.