DNS Server Not Responding? 8 Fixes for Windows, Mac and Your Router
Diagnose the DNS error step by step, with practical Windows and Mac commands, reliable DNS resolvers, and checks for your router.
You open a website and get "The DNS server isn’t responding." Your Wi-Fi is connected, other apps may even work, but the browser refuses to load anything.
The good news: this error is almost always fixable in a few minutes, and the website you’re trying to reach is usually fine. The problem sits somewhere between your device, your router and the DNS resolver that translates names like example.com into IP addresses.
This guide walks through the fixes in the order that solves the problem fastest. You’ll also see how to confirm whether DNS is really the culprit before you change anything.
What "DNS server not responding" actually means
DNS (Domain Name System) works like a phone book for the internet. When you type a website name, your device asks a DNS server for the matching IP address. If that server never answers, or answers too slowly, Windows shows the "DNS server isn’t responding" message.
Most home networks hand out the router as the DNS server, and the router forwards your question to your internet provider’s resolver. A failure can happen at any of those steps:
- Your device has a stale or corrupted DNS cache
- Your router is glitching or overloaded
- Your provider’s DNS servers are slow or down
- A VPN, firewall or antivirus is blocking lookups
- An outdated or misbehaving network adapter driver
If you want a refresher on how DNS records work, read our guide to checking DNS records.
Step 0: Work out if it’s one device or every device
This single check saves a lot of time.
- Only one device fails: the problem is on that device (cache, settings, driver, VPN). Start at Fix 1.
- Every device fails: the problem is your router or provider. Jump to Fix 6.
- Only one website fails: it may be that site’s own DNS or hosting. Try it on mobile data. If it works there, the issue is your network.
You can also run our Internet Checker for a quick look at your browser’s connection, or the Wi-Fi Troubleshooter if the whole connection feels unreliable.
Fix 1: Try another browser or device
Open the same site in a different browser, or on your phone using the same Wi-Fi. If it loads, the issue is limited to the first browser or device, which narrows things down fast.
Fix 2: Flush the DNS cache
Your computer stores recent lookups. If one of those entries is bad, it keeps failing until the cache is cleared.
Windows 10 and 11
- Press the Windows key, type
cmd, right-click Command Prompt and choose Run as administrator. - Run:
ipconfig /flushdns
You should see a message saying the DNS Resolver Cache was flushed.
Mac
Open Terminal and run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Then reload the page.
Fix 3: Switch to a public DNS server
If your provider’s resolver is slow or unreliable, a public resolver often fixes the problem immediately and can make browsing feel snappier.
| Provider | Primary | Secondary |
|---|---|---|
| 8.8.8.8 | 8.8.4.4 | |
| Cloudflare | 1.1.1.1 | 1.0.0.1 |
| Quad9 | 9.9.9.9 | 149.112.112.112 |
Windows 11
- Open Settings > Network & internet.
- Choose Wi-Fi (or Ethernet), then your network’s Hardware properties.
- Next to DNS server assignment, click Edit.
- Switch to Manual, turn on IPv4, and enter a preferred and alternate server from the table.
- Save and reload the page.
Windows 10
Open Control Panel > Network and Sharing Center > Change adapter settings. Right-click your connection > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties > Use the following DNS server addresses.
Mac
Go to System Settings > Network, pick your connection, click Details > DNS and add the new addresses.
Fix 4: Release and renew your IP, then reset the network stack
If a bad network configuration is the cause, resetting it clears it out. In an administrator Command Prompt, run these one at a time:
ipconfig /release
ipconfig /renew
netsh winsock reset
netsh int ip reset
Restart your computer afterwards. Your connection will drop briefly while the commands run, which is normal.
Fix 5: Turn off your VPN, firewall or antivirus (temporarily)
Security software and VPNs sometimes intercept DNS requests. To test:
- Disconnect your VPN and try the site again.
- Pause third-party antivirus or firewall protection for a minute and test.
If the error disappears, don’t leave protection off. Instead, update the software or adjust its network or web-protection settings, then switch it back on.
Fix 6: Restart your router and modem
If every device is affected, this is often the real fix.
- Unplug the router and modem from power.
- Wait about 30 seconds.
- Plug the modem in first, wait until its lights settle, then plug in the router.
- Test again after a couple of minutes.
If you’re comfortable logging in to your router, you can also set the public DNS servers from Fix 3 there, so every device on the network uses them.
Fix 7: Update or reinstall your network adapter driver
An outdated driver can cause odd DNS and connectivity failures.
- Right-click the Start button and open Device Manager.
- Expand Network adapters, right-click your Wi-Fi or Ethernet adapter and choose Update driver.
- If that doesn’t help, choose Uninstall device and restart. Windows will reinstall the driver automatically.
Fix 8: Confirm DNS is really the problem
If nothing has worked, test DNS directly instead of guessing. In Command Prompt or Terminal run:
nslookup example.com
- You get an IP address back: DNS is working, so the problem is likely elsewhere (a browser extension, proxy or firewall rule).
- It times out: the resolver you’re using isn’t answering. Switch resolvers (Fix 3) or check your router.
You can also look up a domain’s records with our DNS Checker, which helps rule out a problem with the website’s own DNS setup. If you suspect slow responses rather than total failure, try the Ping / Latency Test and the Internet Speed Test.
Still stuck? Check these last
- Run the Windows Network Troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Network and Internet.
- Contact your internet provider: if every device fails and a router restart doesn’t help, their DNS servers or the line itself may be down.
- Check for carrier-grade NAT or IP conflicts: our guide to private vs public IP addresses explains how these can affect connectivity.
Quick summary
| Symptom | Most likely fix |
|---|---|
| One device only | Flush DNS, switch DNS servers |
| All devices | Restart router, change DNS on the router |
| Started after installing software | Disable VPN, firewall or antivirus to test |
| Slow rather than failing | Switch resolver and run a latency test |
Frequently asked questions
What does "DNS server isn’t responding" mean?
It means your device asked a DNS server to translate a website name into an IP address and didn’t get a usable answer. The website itself is usually fine.
Is "DNS server not responding" caused by my internet provider?
Sometimes. If every device on your network has the problem and restarting the router doesn’t help, your provider’s DNS servers may be down. Switching to a public DNS server usually works around it.
Is it safe to use Google DNS or Cloudflare DNS?
Both are widely used public resolvers. Check each provider’s privacy policy to decide which one suits you.
Will changing my DNS server make my internet faster?
It won’t increase your connection speed, but a faster resolver can make pages start loading sooner because lookups finish quicker.
Why does the error keep coming back?
A recurring error usually points to an unreliable router, a conflicting VPN or security app, or a failing provider resolver. Setting a public DNS on the router and keeping your adapter driver up to date are the most lasting fixes.
Related tools: DNS Checker · IP Lookup · Ping / Latency Test · Wi-Fi Troubleshooter