You click a link and the browser answers with a cold, technical sentence instead of a page: DNS_PROBE_FINISHED_NXDOMAIN, This site can't be reached, Server not found, Your DNS server might be unavailable. The wording changes between Chrome, Firefox, Edge and Safari, but they all mean one thing. Your device asked for the IP address behind a name and didn't get a usable answer.

The fix depends entirely on where the lookup is failing. So begin with the question that saves the most time.

Is it you or the website?

Try three quick things:

  1. Open a few other websites. If only one fails, the issue is probably that domain.
  2. Try the same address on your phone using mobile data, with Wi-Fi off. If it works there, the problem is your network or device.
  3. Ask a different resolver directly: nslookup example.com 1.1.1.1 (replace example.com with the failing site). If that works but the plain nslookup example.com fails, your normal resolver is the culprit.

Roughly speaking, NXDOMAIN means the resolver was told the name doesn't exist, while "not responding" means it got no answer at all. The first usually points at the domain or at a poisoned cache; the second at your connection or resolver.

Fixes when the problem is on your side

Go in this order. The earlier steps are quicker and fix most cases.

1. Check the address for typos

It sounds silly, but a mistyped domain is the most common cause of NXDOMAIN, and browsers sometimes autocomplete to an old, misspelt entry.

2. Restart the router and modem

Unplug both for thirty seconds. Many home routers cache DNS answers and occasionally get stuck.

3. Flush the DNS cache

Clear the stored answers on your device and in the browser. Commands for every system are in our guide to flushing the DNS cache. On Windows it's ipconfig /flushdns.

4. Switch to a different DNS server

If your ISP's resolver is flaky, changing it solves "server not responding" instantly. Set Cloudflare (1.1.1.1) or Google (8.8.8.8) in your network settings. Our comparison of free public DNS servers lists the options, and you can see which server you currently use with the steps in this guide.

5. Turn off VPNs, proxies and "secure DNS"

VPN apps and corporate proxies replace your DNS settings. In Chrome, Settings, Privacy and security, Security has a "Use secure DNS" switch; set it to your usual provider or turn it off to test. Security software that filters web traffic can also block lookups, so try disabling it briefly.

6. Look at the hosts file

A forgotten entry in C:\Windows\System32\drivers\etc\hosts (Windows) or /etc/hosts (Mac and Linux) overrides DNS for that name. Remove any line you didn't expect, save and retry.

7. Try disabling IPv6

Occasionally a network advertises IPv6 DNS servers that don't work. Turning IPv6 off for the adapter, or switching to a resolver you've set manually, can bring things back.

8. Reset the network stack on Windows

From an elevated Command Prompt, run these, then restart:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew

9. Update or reinstall the network driver

If the problem started after an update, or your adapter is missing from Device Manager, fix that last. It's rare, but it does happen.

Fixes when the problem is the website

If other sites work fine and several resolvers fail for the same domain, it's very likely a DNS problem at the site's end. That's no use to you as a visitor, but if it's your website, here's where to look:

  • The domain may have expired. A WHOIS check shows the expiry date and status codes such as clientHold.
  • The nameservers may be wrong. After a migration, the registrar may still list the old provider.
  • The record may be missing or mistyped. Compare what your control panel says with what the world actually receives.
  • DNSSEC may be broken. Validating resolvers return an error, while others work. See our DNSSEC guide.
  • The change may simply not have spread yet. New records and recent edits take time, covered in how long propagation takes.

The quickest way to tell these apart is to run the domain through the DNS checker. If every resolver says "no such domain", the record is missing or the domain is down at the registry. If some answer and others don't, it's caching or DNSSEC. If they all return the same IP and the site still fails, DNS is fine, and the fault is further along: the web server, firewall or certificate.

A short word on what the error names mean

  • DNS_PROBE_FINISHED_NXDOMAIN (Chrome): the lookup completed and the domain doesn't exist, as far as your resolver knows.
  • ERR_NAME_NOT_RESOLVED (Chrome): the name couldn't be resolved at all, often a sign of a connectivity or resolver problem.
  • DNS_PROBE_FINISHED_BAD_CONFIG (Chrome): your DNS settings are missing or wrong.
  • Server not found (Firefox, Safari): the browser's generic version of any of the above.

If nothing works

Test from another network, such as a phone hotspot, and with a different device. If a different network works, the fault is with your ISP or your router. If a different device on the same network works, it's your machine's configuration. If you've got a mail or website problem on top, see the diagnosis steps in our article about DNS and website downtime.