DNS Server Not Responding: How to Fix It on Windows, Mac, and Router

Your Wi-Fi bars are full. The little icon says “Connected.” But every website you try just spins, and then Windows or your browser tells you the DNS server isn’t responding.

It’s one of the most frustrating network errors because it looks like your internet is down, when most of the time it isn’t. Your connection works. One specific lookup step is broken, and that step is usually fixable in a few minutes.

This guide shows you how to confirm it’s really DNS, figure out whether the problem is your computer, your router, or your provider, and fix it on Windows, Mac, and your router.

Quick Answer: What Does “DNS Server Not Responding” Mean, and How Do I Fix It?

What it means: your device asked a DNS server to translate a website name (like google.com) into an IP address, and either got no answer or an unusable one. Without that translation, pages won’t load even though your connection is technically up.

The fastest fixes, in order:

1. Restart your modem and router (unplug for 30 seconds).
2. Flush your device’s DNS cache.
3. Switch to a public DNS server, such as Cloudflare (1.1.1.1) with Google (8.8.8.8) as the backup.

One rule of thumb: if only one device fails, fix that device. If every device on your Wi-Fi fails, fix the router or wait out a provider problem.

What Is DNS?

DNS (the Domain Name System) is the internet’s phone book. You type theinfobits.com; your device asks a DNS server, “what’s the number for that?”; the server answers with an IP address; and your browser connects to it.

When the DNS server is slow, unreachable, misconfigured, or returns a bad answer, you get errors like:

• Windows: “The DNS server isn’t responding” or “Your DNS server might be unavailable”
• Chrome: DNS_PROBE_FINISHED_NO_INTERNET, DNS_PROBE_FINISHED_BAD_CONFIG, or ERR_NAME_NOT_RESOLVED
• Firefox: “Hmm. We’re having trouble finding that site.”
• Safari: “Safari can’t find the server.”

One look-alike to watch for: DNS_PROBE_FINISHED_NXDOMAIN is different. It means the DNS server did answer and said that domain doesn’t exist (often a typo or a dead site). That’s not a “not responding” problem.

Step 1: Confirm It’s Actually DNS (60-Second Test)

Before changing anything, find out what’s actually broken. This test saves you from fixing the wrong thing.

On Windows: open Command Prompt. On Mac: open Terminal. Then run:

ping 8.8.8.8

Then run:

ping google.com

For extra proof, test a different DNS server directly:

nslookup google.com 1.1.1.1

If that works but a plain nslookup google.com times out, your default DNS server is the broken piece, and switching DNS will fix it.

Step 2: Figure Out Where the Problem Lives

Run this quick triage:

A short flat Cat6 Ethernet cable (easily available on Amazon) is the quickest way to rule Wi-Fi in or out, so it’s worth keeping one around.

Public Wi-Fi tip: at hotels and airports, a login page (“captive portal”) can make DNS look broken. Try opening http://neverssl.com to trigger the sign-in page.

Why Does the DNS Server Stop Responding? (Common Causes)

Fix 1 (Everyone): Restart the Modem and Router the Right Way

It sounds basic, but a power cycle clears the router’s DNS relay and refreshes your lease from your provider.

1. Unplug the modem and the router (and any mesh nodes).
2. Wait 30 seconds.
3. Plug in the modem first and wait until its online light is steady (1 to 3 minutes).
4. Plug in the router and wait about 2 minutes.
5. Test again.

If this fixes it, but the problem comes back every few days, see our guide on common router issues. A basic smart plug like an Amazon Smart Plug on a schedule can power-cycle a router automatically, though set it for the middle of the night, not when anyone’s using the internet.

Fix It on Windows (10 and 11)

Work through these in order. Most people are fixed by step 1 or 3.

1. Flush the DNS Cache and Renew Your IP

Open Command Prompt as administrator (search “cmd,” right-click, Run as administrator), then run these one at a time:

ipconfig /flushdns
ipconfig /release
ipconfig /renew

You should see “Successfully flushed the DNS Resolver Cache.” Your connection may drop for a few seconds during release and renew. You need administrator rights, or the flush fails.

2. Run the Windows Network Troubleshooter

Go to Settings → Network & internet → Advanced network settings → Network troubleshooter (or right-click the network icon and choose Troubleshoot problems). It can fix simple adapter glitches. If it can’t, see our guides on Windows network troubleshooting basics and when the Windows network troubleshooter isn’t working.

3. Change Your DNS Server

This is the fix that works most often when the problem is your provider’s DNS.

Windows 11:

1. Open Settings → Network & internet.
2. Choose Wi-Fi (or Ethernet), then open your connection’s Hardware properties (or the network’s properties page).
3. Next to DNS server assignment, click Edit and choose Manual.
4. Turn on IPv4.
5. Enter a Preferred DNS and an Alternate DNS (see the table below).
6. Set DNS over HTTPS to On (automatic template) only for providers Windows recognizes; otherwise leave it off.
7. Click Save.

Windows 10:

1. Press Windows + R, type ncpa.cpl, and press Enter.
2. Right-click your active adapter and choose Properties.
3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
4. Choose Use the following DNS server addresses and enter your two servers.
5. Click OK, then flush the DNS cache (step 1).

Which servers to enter:

Pro tip: use two different providers, for example Cloudflare as primary (1.1.1.1) and Google as secondary (8.8.8.8).

In July 2025, Cloudflare’s 1.1.1.1 resolver had a global outage lasting around an hour, and Cloudflare itself suggested switching to another provider in the meantime. A backup from a different company would have kept you online.

One caution: If you choose Quad9 or OpenDNS for their filtering, pair them with a filtering secondary so protection stays consistent. For a deeper comparison, see our guides to the best DNS servers for blocking malware and ads and the best DNS servers for gaming.

Work or school computer? Don’t change DNS on a domain-joined or managed PC. Company logins and internal sites rely on your organization’s DNS, and changing it can break them. Ask your IT team.

4. Reset the Network Stack (Winsock and TCP/IP)

If a cache flush didn’t help, reset the networking components. In an administrator Command Prompt:

netsh winsock reset
netsh int ip reset

Then restart the PC.

For a bigger reset: Settings → Network & internet → Advanced network settings → Network reset → Reset now.

This removes and reinstalls your network adapters and resets networking components to their defaults. It can also remove saved Wi-Fi networks and VPN adapters, so note your Wi-Fi password first.

5. Turn Off VPNs and Proxies (Temporarily)

A VPN, or one that was uninstalled badly, can leave behind DNS settings pointing at a server that no longer exists.

• Disconnect any VPN and test again. Our guide on whether a VPN makes your home Wi-Fi more secure explains how VPNs handle DNS.
• Check Settings → Network & internet → Proxy and turn off Use a proxy server unless you need it.
• Run ipconfig /all and look at the DNS Servers line. If you see an address you don’t recognize, that’s a clue.

6. Check Your Security Software (Without Turning It All Off)

Some antivirus and “web protection” tools intercept DNS. To test:

• Pause the web-shield or network-protection feature briefly, test, and turn it back on.
• Check the app’s settings for a DNS or web filtering option.

Don’t disable Windows Firewall or your antivirus entirely as a “fix,” and don’t leave protection off after testing. If pausing one feature solves it, adjust or reinstall that feature instead.

7. Update or Reinstall the Network Adapter Driver

1. Right-click Start → Device Manager.
2. Expand Network adapters, right-click your Wi-Fi or Ethernet adapter, and choose Update driver.
3. If that doesn’t help, choose Uninstall device, then restart. Windows reinstalls the driver.

Also open the adapter’s Power Management tab and make sure Allow the computer to turn off this device to save power is unchecked.

If a laptop’s built-in Wi-Fi adapter keeps misbehaving even after driver updates, a USB Wi-Fi 6 adapter like UGREEN WiFi Adapter or a USB-C Ethernet adapter like UGREEN USB C to Ethernet Adapter ( both are available on Amazon) is an inexpensive workaround that sidesteps the faulty hardware.

8. Test Turning Off IPv6 (As a Test, Not a Permanent Fix)

Some providers’ IPv6 DNS is flaky, and Windows may prefer it. To test:

1. Press Windows + R, type ncpa.cpl, and press Enter.
2. Right-click your adapter → Properties.
3. Uncheck Internet Protocol Version 6 (TCP/IPv6) and click OK.

If that fixes it, the real problem is your IPv6 DNS. Consider setting IPv6 DNS servers explicitly, or fixing it at the router, rather than leaving IPv6 off forever.

9. Check the Hosts File

Malware and old software can add entries that override DNS. Open Notepad as administrator and open C:\Windows\System32\drivers\etc\hosts. Lines starting with # are comments. Anything else pointing popular sites to odd addresses deserves suspicion.

10. Isolate It with Safe Mode or a Clean Boot

Start Safe Mode with Networking. If DNS works there, a startup program or service is the culprit. A clean boot (disabling non-Microsoft startup items) helps you track it down.

A note on “restart the DNS Client service”: many guides recommend this, but on current Windows versions the Stop and Restart options for the DNS Client service are usually greyed out. Flushing the cache (step 1) achieves the same practical result.

Fix It on Mac (macOS Tahoe, Sequoia, Sonoma, Ventura)

1. Flush the DNS Cache

Open Terminal (Applications → Utilities) and run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Enter your password when prompted. No message appears when it works. This command applies to recent macOS versions, including Tahoe (macOS 26).

2. Change DNS Servers

1. Open the Apple menu → System Settings → Network.
2. Select Wi-Fi (or Ethernet) and click Details.
3. Choose DNS in the sidebar.
4. Click + and add 1.1.1.1 and 8.8.8.8.
5. Remove any old or odd entries (like a leftover VPN address) using −.
6. Click OK.

On macOS Monterey and earlier, the path is System Preferences → Network → Advanced → DNS.

To see which DNS servers your Mac is actually using, run scutil --dns in Terminal.

3. Use Wireless Diagnostics

Hold Option and click the Wi-Fi icon in the menu bar, then choose Open Wireless Diagnostics. It checks signal, interference, and basic connectivity, and it’s useful for flaky Wi-Fi.

4. Check VPNs, Filters, and Privacy Features

• Disconnect any VPN and test. Look in System Settings → VPN.
• Temporarily disable third-party content filters or security apps that manage DNS.
• If you use iCloud Private Relay, try turning it off for testing. Some networks and setups interfere with it.

5. Try a Different Browser and Clear Browser DNS Settings

If other apps work but one browser doesn’t, the browser’s own DNS settings may be the issue. In Chrome, check Settings → Privacy and security → Security → Use secure DNS.

Set it to your current provider, or a known-good one. If it’s pointed at a custom provider that’s unreachable, pages fail while other apps still work.

Fix It on Your Router (Fixes It for Every Device)

If every device on your Wi-Fi is failing, work here. Changing DNS at the router means every phone, TV, and laptop gets the fix automatically.

1. Power Cycle (see Fix 1 above)

2. Change the Router’s DNS Servers

Log in to your router (the address is on its label, often. 192.168.0.1, 192.168.1.1, or 10.0.0.1). Menu names vary, but here’s where to look:

Enter your two servers (for example 1.1.1.1 and 8.8.8.8), save, and reboot the router. Then restart your devices, or reconnect them, so they pick up the new setting.

Provider-supplied routers often lock this setting. If you can’t change DNS there, set it on each device instead, or ask about using your own router in bridge mode. Our guide to ISP router vs your own router in bridge mode explains the trade-offs.

3. Update the Router Firmware

Old firmware can have buggy DNS handling. Follow our router firmware update checklist before and after.

4. Test Router Features That Touch DNS

Features such as built-in malware blocking, parental controls, and DNS filtering can sit between your devices and the internet.

Turn one off for a few minutes and test. If DNS starts working, adjust that feature. See our guides on TP-Link HomeShield, ASUS AiProtection, and Netgear Armor if you use them.

5. Try Disabling IPv6 on the Router (As a Test)

If your provider’s IPv6 is unstable, switching it off in the router settings can reveal whether that’s the cause. If it helps, contact your provider rather than leaving it off permanently.

6. Check for a Provider Outage

Try your phone on mobile data (or use the phone’s hotspot). If sites load there but not on your home Wi-Fi, the problem is your router or provider. Check your provider’s outage page or app, and see our guide on setting up temporary internet service as a backup.

7. Look for Signs of DNS Hijacking

Malware and compromised routers can silently change DNS settings to redirect you to fake sites. Warning signs:

• Your router’s DNS shows addresses you didn’t set and don’t recognize
• Pages redirect to ads or fake login screens
• Browser certificate warnings on sites that were fine before
• DNS settings keep changing back after you fix them

If you see these, change the router’s admin password, update the firmware, and consider a factory reset. See our guide on how to factory reset a router. Also, read if your router is part of a botnet.

8. Factory Reset as a Last Resort

If nothing else works, a factory reset clears every setting. Note your provider login details first, since some providers need them.

9. Consider Whether the Router Is the Problem

If the router drops DNS repeatedly even after updates and resets, it may be failing or outdated. See how long routers last.

If it’s time for a replacement, a budget option like the TP-Link Archer AX21 or a stronger pick like the ASUS RT-AX88U Pro ( you may find both of them on Amazon) gets regular security updates and handles DNS more reliably than a router from several generations ago.

Our roundup of routers with built-in malware protection has more detail.

Phones, Consoles, and Smart TVs

The same issue can hit non-computer devices.

iPhone/iPad: Settings → Wi-Fi → tap the ⓘ next to your network → Configure DNS → Manual → remove old servers, add 1.1.1.1 and 8.8.8.8 → Save.

Android: If you see “Private DNS server cannot be accessed,” your phone’s Private DNS setting points to a hostname that isn’t responding.

Go to Settings → Network & internet → Private DNS (the location varies by phone) and choose Automatic or Off, or set a working provider hostname such as dns.google or one.one.one.one.

Consoles and smart TVs: Most let you enter DNS manually under their network settings. If a console has Wi-Fi trouble, see our guide on PS5 Wi-Fi connection issues.

Which DNS Server Should You Use?

There’s no single best answer. Here’s how to choose:

Privacy note: any DNS provider can see which domains your devices look up. Read each provider’s privacy policy and decide who you trust. Our post on whether routers can track your internet history covers what else sees your activity.

Myth vs. Fact

Myth: “DNS server not responding” means my internet is down.
Fact: Usually your connection works. Only the name-lookup step is failing, and ping 8.8.8.8 will prove it.

Myth: Changing DNS makes my internet much faster.
Fact: It can speed up the lookup step slightly, but it won’t raise your download speed.

Myth: Flushing the DNS cache deletes my browsing history.
Fact: It clears stored name-to-address lookups only. Your history, cookies, and passwords aren’t affected.

Myth: I should turn off my firewall to fix DNS errors.
Fact: Don’t leave protection off. Pause one feature briefly to test, then adjust it.

Myth: It’s always my provider’s fault.
Fact: Often it’s a stale cache, a VPN leftover, or a router glitch, all fixable at home.

Myth: Free public DNS is unsafe.
Fact: Major providers are widely used and reliable. The real trade-off is privacy, not safety, so pick one you trust.

Troubleshooting Matrix

Common Mistakes

• Fixing before diagnosing. Run the ping test first.
• Changing DNS but not flushing the cache. Flush afterward.
• Setting only IPv4 DNS while IPv6 DNS is still broken.
• Using two servers from the same provider, so one outage takes both.
• Disabling the firewall entirely.
• Forgetting managed or work devices need their own DNS.
• Leaving IPv6 off permanently as a fix.
• Ignoring signs of hijacking like unknown DNS addresses.

Expert Tips

• Set DNS at the router when you can. One change fixes every device.
• Use two providers for resilience.
• Write down your original settings before changing anything, so you can revert.
• Test with nslookup google.com 1.1.1.1. It tells you instantly whether your default DNS is the problem.
• Re-check DNS after VPN changes. VPN software is a common source of stale settings.
• Keep your router’s firmware current.

Quick Checklist: What to Try, in Order

• [1] Run ping 8.8.8.8 and ping google.com to confirm it’s DNS
• [2] Test another device and mobile data to locate the problem
• [3] Restart modem and router
• [4] Flush DNS (ipconfig /flushdns on Windows, the dscacheutil command on Mac)
• [5] Switch DNS to two different public providers
• [6] Turn off VPN and proxy
• [7] Pause security software to test
• [8] Reset the network stack (Windows)
• [9] Update drivers and router firmware
• [10] Check for a provider outage
• [11] Look for signs of DNS hijacking

When to Contact Your Provider

If only your home connection fails, other devices fail too, and your phone works on mobile data, call your provider. Tell them: “Pinging IP addresses works, but DNS lookups time out on every device.” That wording gets you past the basic script and points them at DNS.

Conclusion

“DNS server not responding” sounds worse than it is. In most cases, your internet connection is fine, and a single lookup step has stalled. Start with the 60-second ping test, work out whether the problem lives on your device or your router, and then apply the fix at that level.

For most people, a router restart, a DNS flush, and a switch to two public DNS servers solve it for good.

If it keeps coming back, treat that as a sign: an aging router, a flaky adapter, or a provider issue worth raising.

Frequently Asked Questions