DNS Server Not Responding: How to Fix It

What the message means, and the fixes in the order that solves it fastest, for Windows, Mac, phones and consoles.

"DNS server not responding" means your device asked its DNS server for a website's address and got no answer, so names can't be turned into IP addresses even though your connection may work. Most of the time, restarting the router, flushing the DNS cache or switching to a public DNS server (1.1.1.1 or 8.8.8.8) fixes it.

Reading this on the device with the problem?

Then DNS works on it again right now. To see which DNS server answers your lookups, and whether it's your provider's or a public one, run our DNS leak test.

Is It Really DNS?

If you can reach an IP address but not a name, it's DNS; if you can't reach either, it's the connection.

  1. Open a terminal (Windows: Command Prompt; Mac: Terminal) and run ping 8.8.8.8. Replies mean your internet connection works.
  2. Run ping google.com. "Could not find host" or "cannot resolve" while the first ping worked means DNS is the problem: follow the fixes below.
  3. No reply to either: the connection is down. Restart the router and modem, check the cables, and look at your provider's outage page from mobile data.
  4. Only one website fails while others open: the problem is that site's DNS, not yours. See only one website fails.

How to Fix "DNS Server Not Responding", in Order

Try these in order and test after each one: the first three solve most cases.

  1. Restart the router and modem. Unplug them for 30 seconds, plug the modem in first, wait until its lights are steady, then the router. Their DNS relay can hang after days of uptime.
  2. Try another device or network. If your phone on Wi-Fi works but the computer doesn't, the computer is the problem; if nothing at home works but the phone on mobile data does, it's the router or the provider.
  3. Flush the DNS cache. It clears old or broken answers your device remembered: Windows ipconfig /flushdns · Mac sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder · Linux resolvectl flush-caches · Chrome chrome://net-internals/#dns › Clear host cache. Every system, phones and browsers: how to flush DNS.
  4. Switch to a public DNS server. Set Cloudflare (1.1.1.1, 1.0.0.1) or Google (8.8.8.8, 8.8.4.4) on the device or the router: all the addresses and the steps for the router and each system. If sites open now, your provider's DNS server was failing.
  5. Turn off the VPN, proxy or security app. VPNs, ad blockers and antivirus "web protection" often handle DNS themselves; turn them off, test, then update or reinstall the one that breaks it.
  6. Renew your address and reset the network. Windows, in Command Prompt as administrator: ipconfig /release, ipconfig /renew, netsh winsock reset, netsh int ip reset, then restart. Mac: System Settings › Network › Wi-Fi › Details › TCP/IP › Renew DHCP Lease.
  7. Update the network driver (Windows): Device Manager › Network adapters › right-click your Wi-Fi or Ethernet adapter › Update driver, or uninstall it and restart so Windows reinstalls it.
  8. Call your provider. If every device fails, even with a public DNS server and after a router restart, the problem is on their side: an outage or a faulty line.

Steps for Your System

The steps for the system you're using are open below.

Windows 10 and 11
  1. Run the network troubleshooter: Settings › System › Troubleshoot › Other troubleshooters › Network and Internet (it opens in the Get Help app).
  2. Open Command Prompt as administrator and run, one by one: ipconfig /flushdns, ipconfig /release, ipconfig /renew.
  3. Set DNS by hand: Settings › Network & internet › your connection › DNS server assignment › Edit › Manual › IPv4 › 1.1.1.1 and 8.8.8.8.
  4. Still failing: netsh winsock reset and netsh int ip reset, then restart the computer.
Mac
  1. Turn Wi-Fi off and on, then System Settings › Network › Wi-Fi › Details… › TCP/IP › Renew DHCP Lease.
  2. In Terminal: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
  3. Details… › DNS › add 1.1.1.1 and 8.8.8.8.
  4. Check for a VPN (System Settings › VPN, in the sidebar) or a configuration profile that sets its own DNS.
iPhone and iPad
  1. Turn Airplane Mode on and off, or forget the Wi-Fi network and join it again.
  2. Settings › Wi-Fi › ⓘ next to your network › Configure DNS › Manual › add 1.1.1.1 and 8.8.8.8.
  3. Still failing: Settings › General › Transfer or Reset iPhone › Reset › Reset Network Settings (it forgets Wi-Fi passwords).
Android
  1. Turn Airplane mode on and off, or forget the Wi-Fi network and join it again.
  2. Settings › Network & internet › Private DNS: if it's set to a hostname that no longer works, set it to Automatic, or to one.one.one.one or dns.google. The message "Private DNS server cannot be accessed" means exactly this: check the hostname for typos, or try another network, because some Wi-Fi networks block port 853, which encrypted DNS uses (what Private DNS is).
  3. Still failing: Settings › System › Reset options › Reset Bluetooth & Wi-Fi (older Android: Reset Wi-Fi, mobile & Bluetooth; menu names vary by brand).
Consoles and smart TVs
  1. Restart the console or TV and the router.
  2. PS5, "A DNS server can't be used" (NW-102307-3): check the PlayStation Network status page first. Sony's own steps: restart the PS5, use a cable if you can and set up the connection again, then turn the router and modem off for at least 5 minutes; its last step is a static IP (Settings › Network › Settings › Set Up Internet Connection). Setting the DNS by hand often helps too, as Sony suggests for related connection errors: same screen › your network › Advanced Settings › DNS Settings › Manual.
  3. In the network settings, choose manual or advanced setup and set the DNS to 1.1.1.1 and 8.8.8.8 (PlayStation, Xbox, Switch and most TVs allow it).
  4. If the device doesn't allow it, set the public DNS server on the router: it then applies to every device.

DNS Error Messages and What They Mean

Chrome, Edge, Safari, Android and the PS5 show their own messages for the same problem; this is what each one means.

NXDOMAIN is the DNS "name error" answer (RFC 1035): a DNS server did reply, saying the name doesn't exist. "Not responding" is different: no DNS server replied at all. For NXDOMAIN, see DNS_PROBE_FINISHED_NXDOMAIN: it checks whether the site exists.

MessageMeaningFirst fix
DNS_PROBE_FINISHED_NXDOMAINThe DNS server says the name doesn't existCheck the spelling; if the name is right, flush the DNS cache and switch DNS (full fix)
DNS_PROBE_FINISHED_NO_INTERNETNo connection at allRestart the router; ping 8.8.8.8
DNS_PROBE_STARTEDThe browser is still testing why the lookup failedReload; if it stays, restart the router and switch DNS
DNS_PROBE_FINISHED_BAD_CONFIGThe DNS settings on the device are wrong or unreachableSet DNS to automatic or to a public server; flush the cache
DNS_PROBE_FINISHED_BAD_SECURE_CONFIGChrome's secure DNS provider doesn't answer, while Google Public DNS doesChrome: Settings › Privacy and security › Security › Use secure DNS: pick "OS default (when available)" or another provider in "Select DNS provider"
ERR_NAME_NOT_RESOLVEDThe name couldn't be turned into an addressSame as NXDOMAIN: check whether the site exists
"Safari can't find the server"Safari's message for a failed lookupFlush the cache on the Mac, then switch DNS
"Private DNS server cannot be accessed" (Android)The encrypted DNS server set in Private DNS doesn't answer on this networkCheck the hostname, try another network, or set Private DNS to Automatic
"A DNS server can't be used" (PS5, NW-102307-3)The console couldn't use its DNS server to reach PlayStation NetworkCheck the PSN status page, restart the PS5 and the router, then set the DNS manually

Only One Website Fails

If every other site works, the problem is usually that site's own DNS, not yours, and only its owner can fix it.

  • Its name servers are down: NS lookup shows them; if our server gets no answer either, it's on their side.
  • It just moved: a recent DNS change can take a while to reach every resolver; check with the DNS propagation checker, and flush your DNS cache.
  • The domain expired: domain WHOIS shows its expiry date.
  • Your DNS filters it: a filtering resolver (family or malware blocking) or an ad blocker may block it on purpose; try from mobile data.

How to Stop It Happening Again

Set a reliable public DNS server on the router, keep the router's firmware up to date, and restart it now and then.

  • Enter the primary and secondary address of the same provider, so the second one answers when the first doesn't.
  • Pick one that answers every time: the DNS speed test shows how fast each public DNS server is from your connection and how many lookups it answered, next to your current DNS.
  • Update the router's firmware from its admin page (find your router); old firmware is a common cause of a hanging DNS relay.
  • If the router is your provider's and DNS fails every few days, ask the provider for a replacement.
  • If DNS settings change by themselves, check the router for DNS servers you didn't set and change its admin password: see DNS hijacking.

Frequently Asked Questions

What does “DNS server not responding” mean?
Your device asked its DNS server for the address of a site and got no answer, so it can't turn names into IP addresses. Your connection itself may be fine: the DNS server, your router's DNS relay or something on your device is failing. Restarting the router, flushing the DNS cache or switching to a public DNS server fixes most cases.
How do I fix DNS server not responding on Windows 11?
Restart the router, then open Command Prompt as administrator and run ipconfig /flushdns, ipconfig /release and ipconfig /renew. If it still fails, set DNS to 1.1.1.1 and 8.8.8.8 in Settings › Network & internet › your connection › DNS server assignment, then run netsh winsock reset and restart the computer.
Why does my DNS keep failing?
Usually a router that needs a restart or a firmware update, an unreliable DNS server at your provider, or a VPN, proxy or security app that intercepts DNS. If it happens every few days, set a public DNS server on the router and update its firmware.
Is it my router or my internet provider?
If every device at home fails and restarting the router doesn't help, it's usually the provider: check its outage page from your phone's mobile data. If only one device fails, it's that device's settings, a VPN or a security app.
Can changing DNS fix it?
Often, yes: if your provider's DNS server is down or slow, a public one like Cloudflare (1.1.1.1) or Google (8.8.8.8) answers instead. It won't help if the connection itself is down, which you can check with ping 8.8.8.8.
What does “Private DNS server cannot be accessed” mean?
Android can't reach the encrypted DNS server set in Private DNS. Check the hostname for typos, try another network (some Wi-Fi networks block port 853, which encrypted DNS uses) or set Private DNS to Automatic.
How do I fix “A DNS server can't be used” on PS5?
Check the PlayStation Network status page first. Then restart the PS5 and the router (router off for 5 minutes), use a cable if you can, and set the DNS manually to 1.1.1.1 and 1.0.0.1 in the connection's Advanced Settings.
Is “DNS server not responding” a virus?
Almost never. But malware can change DNS settings: if your device or router lists DNS servers you didn't set, change them back, scan the device, and change the router's admin password.

Next steps

Related Tools

DNS Leak Test
Which DNS server answers your lookups.
DNS Lookup
Does a site resolve? Ask the public resolvers.
DNS Speed Test
Which DNS server answers fastest, and every time.
Internet Speed Test
Is your connection itself working well?

Related Guides

Guide Best Free Public DNS Servers
Every address, and which is fastest for you.
Guide How to Flush DNS
The command for every system.
Guide DNS_PROBE_FINISHED_NXDOMAIN
When one site's name isn't found.