DNS Server Unavailable: What It Means & How to Fix It

What "DNS Server Unavailable" Means

When websites stop loading and you run the Windows troubleshooter, it often reports: "Your computer appears to be correctly configured, but the device or resource (DNS server) is not responding" — or simply "The DNS server is unavailable." Browsers show their own versions: ERR_NAME_NOT_RESOLVED in Chrome, or "Hmm, we can't reach this page" in Edge.

DNS (Domain Name System) translates domain names like google.com into IP addresses your device connects to. Every page load starts with a DNS query to the resolver your device is configured to use — normally your router, which forwards queries to your ISP's servers. "Unavailable" means those queries are going unanswered: the server is down, unreachable, or something between you and it is eating the requests.

The good news: because the error is confined to the DNS layer, your underlying connection usually still works — and pointing your device at a healthy public resolver fixes it immediately in most cases.

Why It Happens

Ordered from most to least common:

• Your ISP's DNS resolver is down or overloaded — the default for most home connections, and the single most common cause.

• The router's DNS forwarder glitched — devices send queries to the router; when its forwarding service hangs, every device shows DNS errors while WiFi looks fine.

• Corrupted local DNS cache — your device keeps re-serving failed lookups it cached.

• Antivirus or firewall interception — web-protection modules proxy DNS traffic, and when they misfire, all resolution dies.

• A dead VPN tunnel or leftover proxy — DNS queries route into a tunnel that no longer answers.

• Broken network stack settings (Windows) — corrupted Winsock/TCP-IP configuration after updates or malware cleanup.

• Manually set DNS server that no longer exists — an old office/school/VPN address still configured on the adapter.

Fix 1: Flush DNS and Renew Your Connection

Start by clearing every cached lookup and forcing a fresh DHCP lease — this alone clears stale-cache and stale-lease causes in one pass.

# Windows (Command Prompt as Administrator)
ipconfig /flushdns
ipconfig /release
ipconfig /renew

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Then test resolution directly:
nslookup google.com
# "DNS request timed out" = server still unreachable → Fix 2

If nslookup now answers, browse normally — you're done. If it times out, your configured DNS server is genuinely unreachable; move to Fix 2. For a full per-platform walkthrough, see how to flush DNS on every OS.

Fix 2: Switch to a Public DNS Server (Fixes Most Cases)

If your ISP's resolver is the problem, stop using it. Public resolvers are faster than most ISP DNS servers and run globally redundant infrastructure:

Windows: Settings → Network & Internet → your connection → Edit next to DNS server assignment → Manual → IPv4 on → Preferred 1.1.1.1, Alternate 1.0.0.1 → Save.

macOS: System Settings → Network → Wi-Fi → Details → DNS → remove old entries, add 1.1.1.1 and 1.0.0.1 → OK.

Android: Settings → Network & Internet → Private DNS → hostname one.one.one.one. iPhone: Settings → Wi-Fi → (i) → Configure DNS → Manual.

Which resolver answers fastest depends on where you live — benchmark them from your own connection in 30 seconds with the DNS Speed Test.

Fix 3: Restart the Router

When every device in the house shows DNS errors at once, the router's DNS forwarder is the prime suspect — it hangs while the WiFi radio keeps broadcasting happily.

Unplug the router (and modem) for 30 seconds, plug back in, and wait 2–3 minutes. If DNS dies again within days, stop depending on the router's forwarder: set public DNS directly on your devices (Fix 2) or in the router's own settings (Fix 6) so queries skip the flaky middleman.

Fix 4: Disable Antivirus Web Protection, VPN, and Proxies

Security software sits directly in the DNS path more often than people realize. Antivirus "web shield" modules intercept DNS to filter malicious sites — when the module breaks, DNS breaks with it. Temporarily disable the web-protection component (not the whole antivirus) and test.

Disconnect any VPN and test again — a connected tunnel whose DNS server stopped answering kills all resolution. Then check for stray proxies: Windows Settings → Network & Internet → Proxy (turn off manual proxy), macOS Network → Details → Proxies (uncheck all).

Fix 5: Reset the Windows Network Stack

If nslookup still fails against 1.1.1.1 directly (Fix 2 didn't help on one Windows machine), the network stack itself may be corrupted. Reset it:

# Command Prompt as Administrator — then restart the PC
netsh winsock reset
netsh int ip reset
ipconfig /flushdns

This rebuilds the socket and TCP/IP configuration that all DNS queries pass through. It's safe, takes one restart, and repairs damage left behind by uninstalled VPNs, network "optimizer" tools, and malware cleanups.

Fix 6: Set Public DNS on the Router Itself

Changing DNS on the router fixes every device on the network at once — phones, TVs, consoles included. Log into the router admin (gateway IP, commonly 192.168.1.1 or 192.168.0.1), find DNS settings under WAN/Internet or DHCP/LAN, and replace the ISP defaults with 1.1.1.1 and 8.8.8.8.

Note: some ISP-locked gateways (notably AT&T's BGW series) don't allow changing the DNS they hand out — in that case set DNS per device instead, as explained in our AT&T DNS servers guide.

Fix 7: Test in Safe Mode with Networking (Windows)

Still broken on one PC? Boot into Safe Mode with Networking (hold Shift while clicking Restart → Troubleshoot → Advanced options → Startup Settings). Safe Mode loads Windows without third-party services and drivers.

If DNS works in Safe Mode, some installed software is intercepting it in normal mode — antivirus, VPN clients, or "web filtering" tools are the usual suspects. Uninstall or update the most recently added one. If DNS fails even in Safe Mode, the stack reset (Fix 5) and network driver reinstall are next.

Fix 8: When It's Genuinely Your ISP

ISP resolver outages are real and surprisingly frequent — regional DNS failures that take every default-configured customer offline while the network itself runs fine. The tell: everything works the moment you switch to 1.1.1.1 or 8.8.8.8.

You can simply stay on public DNS permanently (most power users do — it's faster anyway), or report the outage so the ISP fixes their resolvers. Check your provider's status page or Downdetector for confirmation, and see our guide to fixing 'DNS server not responding' for ISP-specific steps.

How to Verify the Fix Worked

Confirm resolution directly instead of just reloading pages:

# Ask your current resolver:
nslookup example.com
# The "Server:" line shows WHICH resolver answered

# Ask a public resolver directly (bypasses your settings):
nslookup example.com 1.1.1.1

# If the second works and the first doesn't,
# your configured DNS server is still the problem — redo Fix 2.

And to confirm a specific website resolves for the rest of the world (not just for you), run it through DNS Robot's global DNS lookup — it queries 30+ servers worldwide and shows exactly what each one answers.