Error fix

How to fix “DNS_PROBE_FINISHED_NXDOMAIN

DNS says the hostname does not exist—typo, expired domain, or broken DNS records.

Updated Apr 20, 2026

Tools that help with this

Fastest fix

Start here first. Step 1 fixes most cases—then work down the list.

  1. Confirm the exact hostname and try a public resolver (dig/nslookup).
  2. Check registrar expiry and NS delegation to your DNS provider.
  3. After changes, wait for TTL propagation before retesting.

What this means

NXDOMAIN means the resolver got a negative answer: no records for that name. The problem is naming, not HTTP yet.

Common causes

  • Typos and expiry

    Wrong subdomain, expired registration, or stale local hosts file.

  • DNS config

    Missing A/AAAA/CNAME at the DNS host or wrong nameservers.

Step-by-step fix

  1. Verify DNS end to end

    1. Confirm the exact hostname and try a public resolver (dig/nslookup).
    2. Check registrar expiry and NS delegation to your DNS provider.
    3. After changes, wait for TTL propagation before retesting.

FAQ

NXDOMAIN on Wi‑Fi only?
Try another resolver or disable VPN; captive portals can break DNS.
Works on phone but not desktop?
Flush local DNS cache and compare /etc/hosts or enterprise DNS policies.
Subdomain NXDOMAIN?
Add explicit records or CNAME; apex and www do not auto-cover all subdomains.

Still stuck? Try these related fixes next.

Edit your error

Tweak the message and run again—we'll match an existing fix or generate a new page.

Original error message
DNS_PROBE_FINISHED_NXDOMAIN
Fix another errorHTTP status codesURL status checkerRedirect checkerAll tools