Router DNS Error, DNS Server Not Responding, Fixed

A DNS error means your device is online but cannot turn website names into addresses, so nothing loads even though the connection itself works. The usual message is “DNS server not responding” or “DNS_PROBE_FINISHED_NXDOMAIN”. If every device shows the error, fix it at the router. If only one device shows it, fix that device.

The fix, in order

  1. Confirm it is DNS, not the connection. Open a terminal and run ping 8.8.8.8. If you get replies, the internet works and DNS is the problem. You can also check whether a domain name resolves at all with the DNS lookup tool. If that ping also fails, the connection itself is down, see the router no internet guide instead.
  2. Restart the router and modem. Unplug both for 60 seconds, plug the modem back in first, wait for its lights to settle, then plug the router back in. This clears the router's DNS cache, which is the most common router-level cause.
  3. Flush the DNS cache on the device. On Windows, open an admin Command Prompt and run ipconfig /flushdns. On a Mac, run sudo dscacheutil -flushcache in Terminal. Then close and reopen the browser.
  4. Switch to a public DNS resolver. On the device, set the DNS server to Cloudflare's 1.1.1.1 with 1.0.0.1 as the alternate, or Google's 8.8.8.8 with 8.8.4.4 as the alternate. In Windows this is under Settings, Network and internet, your connection, DNS server assignment, Edit, Manual.
  5. Set the public DNS on the router instead. If every device shows the error, sign in to the router admin page, find the DNS settings under Internet, WAN, or DHCP, and enter the same public addresses there. Save and restart the router. Every device then uses the new resolver automatically.
  6. Check for leftovers from a VPN or security tool. A VPN, a parental control app, or a security tool can leave a dead DNS address configured on the device. Remove old VPN profiles and check the DNS settings for stale entries.
Only change DNS settings on your own devices and your own router. Never accept a DNS change suggested by a pop-up, an email, or a caller claiming to be support, that is a common way to redirect your traffic.

If it still happens

If a public DNS resolver, a fresh router restart, and a second device all still fail, the problem is upstream. Your provider's network may be blocking or failing to route DNS traffic. Contact your provider through its official support channel and tell them that ping to 8.8.8.8 works but name lookups fail, that detail points them at DNS rather than the line.

Common questions

Is it safe to change my DNS to 1.1.1.1 or 8.8.8.8? Yes. Cloudflare's 1.1.1.1 and Google's 8.8.8.8 are free, widely used public resolvers. Changing DNS only affects how names are looked up, and you can switch back to automatic at any time.

Why does DNS fail on every device at once? Because every device uses the router, which forwards lookups to your provider's DNS server. If that server is down or the router's DNS cache is stale, every device fails together. Setting public DNS on the router fixes all of them at once.

What does DNS_PROBE_FINISHED_NXDOMAIN mean? It means the DNS lookup said the name does not exist. It is often a stale cache, a typo in the address, or a DNS server problem rather than the site being down. Flush the cache and try a public resolver before assuming the site is gone.

Related guides

Router Has No Internet · Router Admin Page Not Loading · ERR_INTERNET_DISCONNECTED · Router Slow Wi-Fi

Was this helpful?