Skip to content
Website Rescue Rescue

DNS and Domain Problems

DNS_PROBE_FINISHED_NXDOMAIN

Intermediate Risk: medium

Last reviewed

Hosting access may not be needed Database access usually not needed

Direct answer

DNS_PROBE_FINISHED_NXDOMAIN means the browser asked DNS for your hostname and got “this name does not exist”—usually an expired domain, typo in the URL, wrong nameservers, or a missing A/AAAA/CNAME record. Confirm the domain is registered and live in a public lookup, then fix registrar DNS or nameservers before chasing WordPress or hosting settings.

Chrome and other Chromium browsers show DNS_PROBE_FINISHED_NXDOMAIN when the resolver returns NXDOMAIN instead of an IP address. The site never reaches your hosting account, so plugin fixes and SSL toggles will not help. This guide separates real domain/DNS failures from local cache and typo problems so you restore resolution first.

Intermediate

What the error means

NXDOMAIN is an authoritative DNS answer: the queried name is not in the DNS tree (or the resolver believes it is not). That is different from a timeout, SERVFAIL, or a site that resolves but returns HTTP 500. Chromium surfaces the condition as DNS_PROBE_FINISHED_NXDOMAIN; other browsers may say “server IP address could not be found” or ERR_NAME_NOT_RESOLVED for the same class of failure. Common triggers include an expired or deleted registration, nameservers still pointing at a cancelled host, a subdomain without records, or a mistyped hostname. Local OS or ISP DNS cache can also keep showing NXDOMAIN briefly after you already fixed the live zone.

Common symptoms

  • Chrome shows DNS_PROBE_FINISHED_NXDOMAIN and the page never loads HTML
  • Other networks or phones also fail to resolve the same hostname
  • ICANN Lookup or dig/nslookup reports NXDOMAIN or no A/AAAA answers
  • www works but the apex (or the reverse) does not, or a subdomain alone fails
  • Email and website both broke after a nameserver or domain transfer change
  • The domain shows expired, redemption, or parked status at the registrar
  • Clearing browser cache alone does nothing until DNS or registration is fixed

Most likely causes

  1. 01 Domain registration expired, suspended, or still in transfer limbo
  2. 02 Nameservers set to the wrong host or left on a cancelled DNS provider
  3. 03 Missing or deleted A/AAAA/CNAME records for the hostname visitors type
  4. 04 Typo in the URL, wrong TLD, or an old marketing link to a retired subdomain
  5. 05 Stale local DNS cache or ISP resolver still holding a prior NXDOMAIN answer
  6. 06 DNSSEC misconfiguration causing validation failure that looks like “name not found” in some resolvers
  7. 07 Registrar “parking” or hold status preventing the zone from publishing

What changed before the problem started

  • Domain auto-renew failed or the card on file expired
  • Nameservers moved during a host migration or Cloudflare onboarding
  • Someone deleted apex or www records while editing DNS
  • Domain transfer completed but DNS was never rebuilt at the new registrar
  • A subdomain or staging hostname was advertised before records existed
  • Local machine or router DNS was changed or is caching aggressively

Troubleshooting steps

  1. 01

    Confirm the exact hostname and try another network

    Copy the URL carefully (including www vs non-www and the TLD). Test on phone cellular data or another location. If every network fails the same way, treat it as authoritative DNS/registration—not a single PC cache issue.

  2. 02

    Check registration status in ICANN Lookup

    Look up the domain at ICANN’s lookup tool and note registrar, expiry, and status codes. If the domain is expired, pending delete, or clientHold, renew or resolve the hold with the registrar before editing hosting panels.

  3. 03

    Verify nameservers match where you edit DNS

    Registrar nameserver fields must match the provider whose DNS dashboard you are changing (host, Cloudflare, or registrar DNS). Editing records in the wrong panel has no effect on live resolution.

  4. 04

    Restore apex and www records

    Publish an A/AAAA (or ALIAS/ANAME where supported) for the apex and a matching record or CNAME for www pointing at the correct host. Wait for TTL, then re-check with dig/nslookup against a public resolver such as 1.1.1.1.

  5. 05

    Flush local DNS after the live zone looks correct

    On Windows run `ipconfig /flushdns`; on macOS use `dscacheutil -flushcache` (or the current OS equivalent). Also try an Incognito window. Do not keep changing nameservers while waiting—propagation confusion makes NXDOMAIN last longer.

  6. 06

    Rule out typos and abandoned hostnames

    Compare marketing links, QR codes, and email signatures against the registered domain. Retire or redirect old subdomains that no longer have records instead of leaving visitors on NXDOMAIN.

When to stop troubleshooting

Escalate if the registrar account is locked, the domain is in redemption or dispute, DNSSEC repairs are outside your access, or nameserver changes were made by a vendor you cannot reach. Bring ICANN lookup screenshots, current nameserver list, and dig output from two public resolvers.

Information to collect before requesting help

  • 01 Exact hostname that shows DNS_PROBE_FINISHED_NXDOMAIN
  • 02 Whether www, apex, and subdomains behave differently
  • 03 ICANN Lookup status, expiry date, and registrar name
  • 04 Current nameserver hostnames from the registrar
  • 05 dig/nslookup output from a public resolver
  • 06 Recent domain renewals, transfers, or nameserver edits
  • 07 Whether email failed at the same time as the website

How a professional repairs the problem

We confirm whether the failure is registration, nameservers, missing records, or local/ISP cache. Then we restore a valid zone at the authoritative DNS host, verify public resolution, flush or wait out stale caches, and only after the hostname resolves do we validate hosting document root and WordPress URLs.

Frequently asked questions

Is DNS_PROBE_FINISHED_NXDOMAIN a WordPress error? +
No. The browser never reached WordPress. Fix domain registration and DNS first; WordPress admin, plugins, and themes are irrelevant until the name resolves to an IP.
How is NXDOMAIN different from ERR_CONNECTION_TIMED_OUT? +
NXDOMAIN means DNS said the name does not exist. A timeout usually means an IP was found (or partially resolved) but the host did not answer on the network path.
Why does my phone work but my office PC does not? +
Often local or ISP DNS cache. After the live zone is correct, flush the PC cache or wait for the ISP TTL. If ICANN shows expired, every network should eventually fail—renew first.
Can a typo cause this exact Chrome message? +
Yes. A wrong TLD or misspelled hostname returns NXDOMAIN just like an expired domain. Always verify the registered spelling before changing production DNS.
Will buying SSL or changing PHP fix NXDOMAIN? +
No. Certificates and PHP run after DNS resolution succeeds. Spend effort on registrar status and DNS records instead.
How long after fixing DNS should Chrome work? +
Often minutes with low TTLs; sometimes up to the old TTL (commonly up to 24–48 hours for stubborn ISP caches). Public resolvers usually update sooner than residential ISPs.

Repair dispatch

Still Need Help Fixing Your Website?

If you are not comfortable editing website files, changing server settings, repairing a database, or troubleshooting a live website, professional help may prevent additional damage or downtime. We will review the problem before accepting the repair.

  • You will receive a clear explanation of the likely cause.
  • We will tell you if the issue falls outside our repair scope.
  • No additional work will be performed without approval.
  • A backup should be created whenever access and website condition allow it.
Emergency repair Request diagnosis

Do not share passwords through an unencrypted contact form.

Written by Website Rescue

Last reviewed

Platform note: Full rescue available for WordPress and self-hosted sites. Wix, Squarespace, Webflow, Weebly, and similar closed builders have very limited backend access — fixes may not be possible. I will tell you honestly before we start.