Skip to content
Networking

Fix "DNS_PROBE_FINISHED_NXDOMAIN"

DNS_PROBE_FINISHED_NXDOMAINserver IP address could not be foundthis site can't be reached
7 min read Updated 12 June 2026 ESAGAMES Team

This error means your computer asked DNS for the domain and got "no such domain" (NXDOMAIN). It's either your DNS cache/settings, or the domain's records. Here is how to tell and fix it.

Is it just you, or everyone?

Check the domain from another network/device or an online DNS tool. If it works elsewhere, it's your machine; if it fails everywhere, it's the domain's DNS.

Fix it on your side

Flush your DNS cache and try a public resolver (1.1.1.1 / 8.8.8.8):

# Windows
ipconfig /flushdns
# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
# Linux
sudo systemd-resolve --flush-caches

Fix it on the domain side

  • The domain has no A record — add one pointing to your server. See pointing a domain (A record).
  • The domain expired or its nameservers are wrong — check the registrar.
  • A recent DNS change hasn't propagated yet — give it time.
NXDOMAIN = "no such name"

It specifically means the DNS lookup returned no record, not that the server is down. The problem is DNS resolution, not the web server.

NXDOMAIN = the name didn't resolve. Flush your DNS and try 1.1.1.1; if it fails everywhere, fix the domain's A record/nameservers.

Cause: DNSSEC misconfiguration

If DNSSEC is enabled at the registrar but the DS records don't match what the nameservers actually sign, validating resolvers reject the domain outright, which can also show as NXDOMAIN-like failures. If you recently touched DNSSEC settings, that's a strong suspect; disabling it temporarily helps isolate the cause.

Cause: a typo or a missing subdomain record

A single-letter typo, or trying to reach a subdomain (like shop.example.com) that has no record of its own, produces this exact error even though the base domain is fine. Double-check the exact hostname, and add a record for the subdomain if one is missing.

How to prevent NXDOMAIN issues

  • Renew domains well before expiry, ideally with auto-renew on.
  • Keep nameservers and DNS records documented somewhere outside the registrar, in case of account issues.
  • Avoid touching DNSSEC unless you're confident in the DS record chain.
  • Use a monitoring tool that alerts on DNS resolution failures, not just HTTP downtime.

Related errors

If the domain resolves but the connection then stalls, that's a different problem — see ERR_CONNECTION_TIMED_OUT. If SSL is the issue once the domain does resolve, see SSL / Let's Encrypt renewal. Picking a new host and need DNS set up? See how to choose a web hosting provider.

Domains + hosting, DNS managed

Host with us and we manage your DNS records, so domains resolve correctly — on protected NVMe.

See web hosting
FAQ

Frequently asked questions

What does DNS_PROBE_FINISHED_NXDOMAIN mean?

Your computer asked DNS for the domain and got "no such domain" back. Either your local DNS cache/settings are bad, or the domain has no valid DNS record (missing A record, expired, or wrong nameservers).

How do I fix it on my computer?

Flush your DNS cache (ipconfig /flushdns on Windows) and switch to a public resolver like 1.1.1.1 or 8.8.8.8. If the site then loads, it was a local DNS issue.

Why does only my site show NXDOMAIN?

If it fails for everyone, the domain's DNS is the problem — a missing A record, expired domain, or wrong nameservers. Check the registrar and add/fix the A record.

Can DNSSEC cause DNS_PROBE_FINISHED_NXDOMAIN?

Yes — if DNSSEC is enabled at the registrar with DS records that don't match what your nameservers actually sign, validating resolvers will refuse to resolve the domain at all. This is a less common but real cause worth checking if records look otherwise correct.

How long does a new DNS record take to work everywhere?

Usually minutes to a few hours, but full global propagation can take up to 24-48 hours in rare cases, especially if the previous record had a long TTL. Lower the TTL in advance of a planned change if you can.

Why does the domain resolve on my phone's data but not on Wi-Fi (or vice versa)?

That points to a local DNS cache or resolver issue on one network rather than the domain itself — flush DNS on the affected network/device and try a public resolver like 1.1.1.1 there.

Further reading

Go deeper on this

Guides and explainers that pair with this fix — from our guides and blog.

Knowledge base

Related articles

Skip the troubleshooting

Managed, protected hosting in Frankfurt — we handle the Linux, the network and the DDoS so you don't have to.

Payments Secure checkout with cards, banking apps and digital wallets.

Choose the payment flow that fits your stack and region without leaving the platform.

Pay by Zen Visa Mastercard Paysafecard PaysafeCash Skrill Trustly Bancontact UnionPay iDeal WebMoney