IT Error Decoder

How to Fix DNS_PROBE_FINISHED_NXDOMAIN

Error message

This site can't be reached. DNS_PROBE_FINISHED_NXDOMAIN. <hostname>'s server IP address could not be found.

If you're seeing "DNS_PROBE_FINISHED_NXDOMAIN", you're not alone. Here's what it means, why it happens, and the steps to resolve it.

What this error means

Your machine asked a DNS server for the site's IP, and the server replied that no such name exists. Either the name is wrong or your DNS resolver is broken.

Why this happens

Typo in the domain, a custom DNS resolver that's down or misconfigured, a VPN steering DNS to an internal resolver that doesn't know the public name, or a recent domain expiration.

Step-by-step fix

  1. Try a different known-good site to isolate the issue.

  2. Flush the DNS cache and retry.

    command
    ipconfig /flushdns
  3. Test resolution directly against a public resolver to see if it's a local DNS problem.

    command
    nslookup <hostname> 1.1.1.1
    nslookup <hostname> 8.8.8.8
  4. If those work but your default doesn't, fix or change your DNS settings (Network adapter → Properties → IPv4 → DNS).

Affected products

Windows Admin

Still broken? Try these

  • Disconnect VPN and retest — corporate DNS often only resolves internal names.
  • Confirm the domain hasn't expired with a public WHOIS lookup.
  • Check `hosts` file at `C:\Windows\System32\drivers\etc\hosts` for stale overrides.

Related errors

Frequently asked questions

What does "DNS_PROBE_FINISHED_NXDOMAIN" mean?

Your machine asked a DNS server for the site's IP, and the server replied that no such name exists. Either the name is wrong or your DNS resolver is broken.

What causes "DNS_PROBE_FINISHED_NXDOMAIN"?

Typo in the domain, a custom DNS resolver that's down or misconfigured, a VPN steering DNS to an internal resolver that doesn't know the public name, or a recent domain expiration.

How do I fix "DNS_PROBE_FINISHED_NXDOMAIN"?

1. Try a different known-good site to isolate the issue. 2. Flush the DNS cache and retry. 3. Test resolution directly against a public resolver to see if it's a local DNS problem. 4. If those work but your default doesn't, fix or change your DNS settings (Network adapter → Properties → IPv4 → DNS). Always test changes in a non-production environment first.

Browse more errors in Windows Admin: Fix Windows administration errors. Access denied, RPC server unavailable, trust relationship failures, Group Policy errors, and network path issues. Or paste your own error into the error decoder tool to find a match. You can also go back to the homepage to browse common errors by topic.