DNS Server Not Responding: What It Means and 7 Ways to Fix It

You open your browser and get "DNS Server Not Responding." Your Wi-Fi shows as connected. Other devices on the same network may work fine. It's frustrating precisely because it looks like there's internet but websites won't load.

The good news: this error is almost always solvable in under 10 minutes, and 90% of cases are resolved by the first three fixes below.

What DNS Is and Why This Error Happens

DNS (Domain Name System) is the internet's phone book. When you type "google.com," your device contacts a DNS server to look up the IP address (like 142.250.80.46) associated with that name. Without a working DNS server, your browser doesn't know where to send the request — even if your connection to the internet itself is fine.

This error appears when your device can't reach its configured DNS server — which is usually your router, which in turn uses your ISP's DNS servers. The chain can break at any link.

Fix 1 – Restart Router and Modem (Properly)

Most people restart a router by unplugging it. But if you have a separate modem and router, the restart order matters. Unplug both. Wait 30 seconds. Plug in the modem first, wait for it to fully connect (usually 60–90 seconds until the internet light is solid), then plug in the router. This ensures the router establishes its connection to the modem cleanly rather than connecting before the modem is ready, which can cause DNS assignment failures.

Fix 2 – Flush the DNS Cache

Your computer caches DNS lookups to speed up browsing. If those cached entries become stale or corrupted, you get DNS errors even when the DNS server itself is working fine. Open Command Prompt as Administrator and run:

Restart your browser after running these. This takes about 60 seconds and fixes a significant portion of DNS errors that appear suddenly on a previously working connection.

Fix 3 – Change Your DNS Server

If your ISP's DNS server is down or overloaded, switching to a public DNS server like Google's (8.8.8.8) or Cloudflare's (1.1.1.1) bypasses the problem entirely. Go to Settings → Network and Internet → Wi-Fi → Hardware Properties and click Edit next to DNS server assignment. Switch to Manual and enter:

• Preferred IPv4 DNS: 1.1.1.1 (Cloudflare — fastest in most regions)
• Alternate IPv4 DNS: 8.8.8.8 (Google)

Save and test immediately. If websites load now, your ISP's DNS was the problem. You can keep these settings permanently — Cloudflare and Google's DNS are generally faster and more reliable than ISP defaults.

Fix 4 – Reset Your Network Adapter

Open an elevated Command Prompt and run:

Restart your PC afterward. These commands reset the TCP/IP stack and Winsock catalog to factory defaults, which resolves DNS errors caused by corrupted network configuration at the Windows networking stack level.

Fix 5 – Temporarily Disable IPv6

DNS over IPv6 can conflict with some router configurations, causing resolution failures even when IPv4 DNS works. Go to Control Panel → Network and Sharing Center → Change adapter settings. Right-click your Wi-Fi adapter → Properties. Find Internet Protocol Version 6 (TCP/IPv6) and uncheck it. Click OK and test. If it fixes the problem, your router's IPv6 DNS configuration is the root cause — check your router's DNS settings for proper IPv6 server configuration.

Fix 6 – Update or Reinstall the Network Driver

A buggy or outdated Wi-Fi driver can cause DNS lookup failures. Open Device Manager, expand Network Adapters, right-click your Wi-Fi adapter and select Update driver. If no update is available through Windows, go to your laptop or motherboard manufacturer's website and download the latest driver for your specific model.

If the driver was recently updated and DNS started failing afterward, roll it back: Device Manager → right-click adapter → Properties → Driver tab → Roll Back Driver.

Fix 7 – Check Router Firewall Settings

Some routers have firewall rules that block DNS queries — either through an overly aggressive security setting or a misconfiguration. Log into your router admin panel (usually 192.168.1.1 or 192.168.0.1 in your browser). Look for Firewall or Security settings and check whether DNS port 53 is blocked. Also look for any parental control or content filtering features that route DNS through a third-party DNS proxy — these can fail and cause the "not responding" error when that proxy goes down.