DNS_PROBE_FINISHED_NXDOMAIN: What It Means and How to Fix It
DNS_PROBE_FINISHED_NXDOMAIN generally means the DNS lookup did not produce a usable domain name result. The problem can be local to one device or network, or it can come from the domain’s public DNS configuration.
1. Check whether the domain resolves publicly
Look up the domain’s A, AAAA and CNAME records. If public resolvers cannot find the hostname, changing browsers will not fix the underlying domain configuration.
2. Verify the nameservers
Confirm that the registrar delegates the domain to the DNS provider where you are actually managing records. Editing records in an old or inactive DNS dashboard is a common cause of persistent failures.
3. Check recent DNS changes
If records or nameservers were changed recently, compare results across resolvers. Mixed answers can indicate cached data while the new configuration becomes visible.
4. Rule out a local cache problem
If ZoneCheckr and other networks resolve the domain correctly but one device does not, restart the browser or device and clear the operating system’s DNS cache where appropriate. Testing another network can help separate a local resolver problem from a public DNS problem.
5. Check the exact hostname
The root domain and www are separate DNS names. A working root domain does not automatically mean the www hostname exists, and the reverse is also true.
Check your domain
Use ZoneCheckr to inspect the live configuration before making changes.
Run DNS LookupStill stuck? Get technical help with your domain →