DNS Server Not Responding: What It Means and How to Fix It

“DNS server not responding” means your computer can’t reach the DNS server that translates domain names into IP addresses. Without DNS, web addresses don’t resolve and sites don’t load – even if your internet connection itself is working fine. Here’s how to diagnose and fix it.

Understanding what’s happening

DNS (Domain Name System) is like a phone book for the internet. When you type “google.com,” your computer asks a DNS server for the IP address associated with that name. If the DNS server doesn’t respond, the translation fails and the page doesn’t load.

The issue could be with your ISP’s DNS servers being down, your router’s DNS settings, a local network configuration problem, or Windows’ own network stack.

Quick test first

Open Command Prompt and run: ping 8.8.8.8

If this works (you get replies), your internet connection is fine – the problem is specifically DNS, not connectivity. If this also fails, the problem is with your internet connection more broadly.

Fix 1: Use a different DNS server

Your router likely uses your ISP’s DNS servers by default. Switching to a public DNS server is the fastest fix and often permanent solution:

Go to: Control Panel > Network and Internet > Network and Sharing Center > click your connection > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties > Use the following DNS server addresses

Set to:

  • Preferred: 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare)
  • Alternate: 8.8.4.4 or 1.0.0.1

Click OK. Open a browser and test. Public DNS servers are generally faster and more reliable than ISP defaults.

Fix 2: Flush DNS cache

Windows caches DNS results locally. A corrupted cache can cause DNS failures even when the server is reachable.

Open Command Prompt as administrator and run:

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

Restart after running these commands.

Fix 3: Restart router and modem

Power cycle your router and modem (unplug, wait 30 seconds, plug modem in first, then router). Router DNS caches can become corrupted and a restart clears them.

Fix 4: Update or reinstall network adapter driver

Device Manager > Network adapters > right-click your adapter > Update driver. An outdated or corrupted network driver can cause DNS resolution failures even with correct settings.

Fix 5: Check for VPN or security software conflicts

VPNs, some antivirus programs, and parental control software can intercept DNS queries and cause failures. Temporarily disable any such software and test. If DNS works with it disabled, that software’s DNS settings need adjustment.

Switching to 1.1.1.1 or 8.8.8.8 is the fix I reach for first because it’s immediate and usually works. ISP DNS servers go down or get flaky surprisingly often. Public DNS servers have much better uptime and are typically faster. It’s worth doing as a permanent change even if you’re not currently having issues.

the ping 8.8.8.8 test first is exactly right. if that works, you know your internet connection is fine and the problem is dns specifically. that narrows down the troubleshooting immediately. if ping also fails, the problem is upstream and changing dns settings won’t help.