DNS Server Not Responding: Three Commands Find the Cause Before You Click Anything
'DNS server not responding' means your device asked a DNS server to turn a name into an address and got no answer. Three commands tell you whether the fault is your connection, your resolver, or something blocking DNS, and the fix for each is different.

Key takeaways
- 'DNS server not responding' means your device sent a name lookup to its configured DNS server and got no answer, so the connection itself may be fine while every website name fails.
- Three commands split the problem: ping 1.1.1.1 tests the connection, nslookup example.com tests your configured resolver, and nslookup example.com 1.1.1.1 tests a different resolver without changing any setting.
- On Windows, ipconfig /flushdns clears the resolver cache, including negative cache entries, which are remembered failures that can keep a name broken after the server recovers.
- On a Mac, Apple documents sudo killall -HUP mDNSResponder as the command that resets the DNS cache on OS 10.10.4 and later.
- If your resolver is the broken part, point your device at Cloudflare (1.1.1.1 and 1.0.0.1) or Google Public DNS (8.8.8.8 and 8.8.4.4), and give each device a primary and a secondary address.
“DNS server not responding” means your device asked a DNS server to turn a website name into an IP address and never got an answer.
The fix is usually one of three things: flush the cached lookups, restart the router, or point your device at a different DNS server such as 1.1.1.1 or 8.8.8.8. Which one depends on a test that takes about twenty seconds.
Most guides skip that test. They hand you eight fixes in a row and let you click through all of them, including reinstalling network drivers, before you learn whether DNS was ever the problem. I've done that dance. It's a bad way to spend an evening.
A quick refresher so the rest makes sense. DNS, the Domain Name System, is the phone book that turns example.com into a number your computer can connect to. Your device doesn't look names up by itself.
It asks a resolver, a server that does the legwork and caches the result. I covered the full chain in what DNS is and how it works. This article is about the moment that first question goes unanswered.
Run three commands before you fix anything
Here's the thing that makes this error confusing. Your Wi-Fi can be perfectly healthy. Packets can flow. The only thing broken is the name lookup, so the browser reports a DNS problem while your video call keeps running. Three commands separate the cases.
ping 1.1.1.1
nslookup example.com
nslookup example.com 1.1.1.1ping -c 4 1.1.1.1
nslookup example.com
nslookup example.com 1.1.1.1That third command works because of how nslookup takes its arguments. The first is the name to look up. The second is the DNS server to ask, and if you leave it out, the tool uses your default one.[1] So you get to compare your resolver against a known-good one, side by side, with no settings changed.
Diagnosis
Which command fails tells you which layer is broken
Run in this order
ping 1.1.1.1Tests the connection, with no DNS involved.nslookup example.comAsks your configured resolver.nslookup example.com 1.1.1.1Asks Cloudflare instead.
Find the first command that fails
A passing ping with a failing lookup is the signature of this error.
What it means
- Ping failsNot a DNS problem. Check Wi-Fi, the router and the cable to the modem.
- Ping works, default lookup fails, Cloudflare lookup worksYour configured resolver is down. Restart the router, then switch DNS servers.
- Both lookups fail, ping worksSomething is blocking DNS itself: a VPN, a firewall or security software.
If the ping fails, stop here. No DNS setting can fix a connection that isn't there.
If the ping fails, you're in a different article. Check the router, check the cable, and read modem vs router if you aren't sure which box does what. Everything below assumes the ping worked.
Flush the DNS cache, and learn why it works
Your device keeps its own memory of recent lookups. That memory also stores failures. Microsoft says it plainly: flushing the resolver cache lets you discard negative cache entries, along with any other entries added dynamically.[2] A negative cache entry is a remembered “that name doesn't exist.”
This is the part that bites people. Your DNS server comes back, you retry the site, and it still fails, because your machine is trusting its own cached failure. Flushing is not a superstition. It's how you make the machine ask again.
ipconfig /flushdnssudo killall -HUP mDNSResponderOn a Mac, the process being nudged is mDNSResponder, the background service that handles name lookups.[3] Older Mac versions used different commands, and Apple's page lists them if you're on something ancient. I haven't tested this on every macOS release, so if it errors on yours, check Apple's page first.
Restart the router, but know what you're restarting
On most home networks your router hands every device its own address as the DNS server. Your laptop asks the router, and the router asks your ISP or a public resolver on your behalf.
That means “DNS server not responding” often names your own router. Its DNS forwarder, a small service that relays your questions upstream, has hung while everything else on it keeps working.
Unplug the router, wait half a minute, plug it back in. It's the oldest advice in networking because it works on exactly this failure. If your internet comes in through a separate modem, restart that too, modem first.
“A passing ping with a failing lookup is the signature of this error. Everything else is guessing.”
Switch to a different DNS server
If the Cloudflare lookup worked and your default one didn't, stop fixing the old resolver and replace it. Two public resolvers do the job, and both publish the addresses you need.
| Provider | IPv4, primary and secondary | IPv6, primary and secondary |
|---|---|---|
| Cloudflare | 1.1.1.1 and 1.0.0.1[4] | 2606:4700:4700::1111 and 2606:4700:4700::1001 |
| Google Public DNS | 8.8.8.8 and 8.8.4.4[5] | 2001:4860:4860::8888 and 2001:4860:4860::8844 |
On Windows 11, open Settings, then Network & internet, then your Wi-Fi or Ethernet connection, then its hardware properties, and edit the DNS server assignment to manual. On a Mac, open System Settings, then Network, pick your connection, open Details, and use the DNS tab.
Google's own instructions walk through the older Control Panel and System Preferences versions of the same screens.[5] The menus move around between releases. The addresses are what matter.
My habit is to use Cloudflare as primary and Google as secondary. Mixing providers means one provider's bad day doesn't take you offline. The trade-off is real, though.
Whoever runs your resolver sees the names you look up, so you're moving that visibility from your ISP to a company you chose. I'm comfortable with that. You should decide for yourself.
Heads up
When both lookups fail but the ping works
This is the odd case in the diagram. Your connection is fine, and even a direct question to Cloudflare gets no answer. Something between your device and every resolver is eating DNS traffic.
Turn off any VPN and retest. Pause third-party firewall or antivirus “web protection” for a minute and retest. If a guest network or hotel Wi-Fi is involved, open any plain web page, because many captive portals block lookups until you accept their terms. Whichever of those flips the result is your answer.
The heavy hammer, and the commands for it
If you've done all of the above and Windows still can't resolve names, Microsoft's own troubleshooting page lists a set of commands to run from an administrator Command Prompt, in this order: netsh winsock reset, netsh int ip reset, ipconfig /release, ipconfig /renew and ipconfig /flushdns.[6] Restart afterward.
The release command drops your current address, and Microsoft warns that it disables TCP/IP on adapters that get their address automatically until you renew.[2] Run the whole set as a unit, don't stop halfway.
The same page offers a Network reset under Settings as a last resort, and it reinstalls your network adapters with default settings, so you may need to set up a VPN client again afterward.[6]
Takeaway
Run ping 1.1.1.1 and two nslookup commands first. They tell you whether to fix the connection, replace the resolver, or hunt for something blocking DNS, and they save you from trying every fix on the internet.
What I'd actually do
I run the three commands, flush the cache, and switch DNS servers on the device that's failing. I leave the router alone unless every device in the house has the problem. After that I set the resolver on the router itself, so every phone and TV gets the fix without anyone touching them.
The error reads like a disaster. It almost never is. It's a phone book that stopped picking up, and you now know how to dial a different one.
Primary sources
- 1.PrimaryMicrosoft Learn, "nslookup". Noninteractive mode: the second parameter names the DNS server to use, and omitting it uses the default server.
- 2.PrimaryMicrosoft Learn, "ipconfig". /flushdns, negative cache entries, and the effect of /release on DHCP adapters.
- 3.PrimaryApple Support, "Reset the DNS cache in OS ". sudo killall -HUP mDNSResponder for OS 10.10.4 and later, plus older version commands.
- 4.PrimaryCloudflare, "1.1.1.1 IP addresses". Standard resolver addresses for IPv4 and IPv6.
- 5.PrimaryGoogle, "Get started with Google Public DNS". Resolver addresses and configuration steps for Windows and macOS.
- 6.PrimaryMicrosoft Support, "Fix Wi-Fi connection issues in Windows". The netsh winsock reset sequence and the Network reset last resort.
Frequently asked questions
- What does DNS server not responding mean?
- It means your device asked a DNS server to translate a website name into an IP address and the server never answered. Your Wi-Fi can still be connected and your IP traffic can still flow. Only the name lookup is failing, which is why sites by name fail while a ping to 1.1.1.1 still works.
- How do I fix DNS server not responding on Windows?
- Run ipconfig /flushdns in Command Prompt, then restart your router, then test with nslookup example.com 1.1.1.1. If that last lookup works while the plain one fails, change your DNS server to 1.1.1.1 and 1.0.0.1 or 8.8.8.8 and 8.8.4.4. If it still fails, run netsh winsock reset and netsh int ip reset from an administrator Command Prompt and restart.
- How do I flush DNS on a Mac?
- Open Terminal and run sudo killall -HUP mDNSResponder, then enter your password. Apple lists that command for OS 10.10.4 and later. It clears the cached answers your Mac is holding, including remembered failures.
- Is it my router or my ISP when DNS is not responding?
- Test with nslookup example.com 1.1.1.1. If that works and your default lookup fails, the resolver your device is configured to use is the problem, which is usually your router or your ISP's server. Restart the router first, then switch the device to 1.1.1.1 or 8.8.8.8. If ping 1.1.1.1 fails too, the connection is down and DNS is not the cause.
- Which DNS server should I use instead?
- Cloudflare (1.1.1.1 and 1.0.0.1) and Google Public DNS (8.8.8.8 and 8.8.4.4) are the two common choices, and both publish IPv6 addresses as well. Either works as a replacement. Using one provider as primary and the other as secondary keeps you covered if one has an outage.
Written by
Tech Talk News Editorial
Computer engineering background. Writes about software, AI, markets, and real estate, and the places where the three meet.
More about the author