Introduction

DNS_PROBE_FINISHED_NXDOMAIN means the requested domain name could not be resolved to a valid DNS record. The browser is not saying the site is slow or blocked; it is saying the name does not exist from the resolver's point of view. That usually points to a registrar, nameserver, or DNS zone problem rather than an application bug.

Symptoms

  • Chrome reports DNS_PROBE_FINISHED_NXDOMAIN
  • The site fails before any page content starts loading
  • The domain returns no answer in public DNS tools
  • Subdomains may fail while the main domain still works, or the reverse
  • The issue appears right after changing registrars, nameservers, or DNS providers

Common Causes

  • The domain expired or was suspended at the registrar
  • Required A, AAAA, or CNAME records were deleted
  • The domain points to the wrong nameservers
  • The DNS zone exists in one provider but the registrar delegates elsewhere
  • Propagation is still in progress after a recent DNS move

Step-by-Step Fix

  1. Confirm the domain is active and not expired in the registrar account.
  2. Check the delegated nameservers at the registrar and compare them with the DNS provider that actually hosts the zone.
  3. Verify that the required root and subdomain records exist in the authoritative DNS zone.
  4. If you recently migrated DNS, make sure the full zone was recreated before switching nameservers.
  5. Test the domain with multiple public resolvers to separate propagation delay from a real configuration error.
  6. Restore missing A, AAAA, or CNAME records for the affected hostname.
  7. Remove obviously stale or conflicting records that point to old infrastructure.
  8. Wait for propagation if you changed delegation, then re-test from browser and DNS tools.
  9. After recovery, document the working nameservers and critical records so the issue is easier to reverse next time.