DNS_PROBE_FINISHED_NXDOMAIN Error: Causes and the Fix

You type in your domain, hit enter, and instead of your site you get a blank Chrome page that says "This site can't be reached - DNS_PROBE_FINISHED_NXDOMAIN." No red padlock warning, no half-loaded page - just a dead end. Here's what actually causes it and how to fix it without guessing.

What DNS_PROBE_FINISHED_NXDOMAIN actually means

NXDOMAIN is short for "non-existent domain." Your browser asked a DNS resolver to translate your domain name into an IP address, and the resolver came back and said the domain doesn't exist - at least not from where it's looking. This is a DNS-layer error, not a server or hosting error. Your VPS or cPanel account could be running perfectly and you'd still see this if the DNS record chain is broken somewhere between your browser and Getwebup's nameservers.

It's easy to confuse this with a server-side 500 error or an SSL warning, but the browser never gets far enough to talk to your server. It stops at the lookup step.

Symptom checklist

• Chrome/Edge/Firefox shows "can't be reached" with DNS_PROBE_FINISHED_NXDOMAIN specifically (not a timeout or connection refused)
• The domain fails from your laptop but a friend on a different network can load it fine, or vice versa
• www.yourdomain.com works but yourdomain.com doesn't, or the reverse
• It started right after you registered a new domain, changed nameservers, or moved hosts

Common causes, ranked by how often we see them

1. Nameservers haven't propagated yet

If you just pointed your domain to Getwebup's nameservers, or changed them at your registrar, the change isn't instant. DNS propagation typically takes 15 minutes to a few hours, but can stretch to 24-48 hours depending on the TTL your old provider had set and how aggressively local resolvers cache records. This is the single most common cause of a fresh NXDOMAIN right after a domain move.

2. The domain was never activated in cPanel/WHM

If you registered the domain but never added it as the primary domain, an addon domain, or a parked domain in cPanel, there's no zone file for it on the server side - even though the nameservers point correctly. Check WHM > DNS Zones or cPanel > Domains to confirm a zone exists.

3. Missing or wrong A record

If you're using third-party DNS (like your registrar's DNS or Cloudflare) instead of Getwebup's nameservers, you need an A record pointing yourdomain.com to your server's IP. No A record for the root domain means the root fails even if www works, since www is usually a separate CNAME or A record.

4. Domain registration actually lapsed or is on hold

An expired domain, or one in a registrar redemption/hold status, will return NXDOMAIN everywhere - not just on your machine. Run a WHOIS lookup to confirm the domain is active and not sitting in "clientHold" or "pendingDelete" status.

5. Local DNS cache or resolver holding a stale answer

Your own machine or router can cache a "doesn't exist" answer and keep serving it even after the real DNS is fixed. This explains why the same domain works on your phone's mobile data but not your home Wi-Fi.

6. A typo in the domain itself

Worth ruling out early - a missing letter, wrong TLD (.con instead of .com), or an old bookmark pointing at a domain you no longer own.

How to diagnose it step by step

1. Confirm the domain resolves from outside your network. Use a third-party checker or run dig yourdomain.com +short from a different connection (mobile data works well for this).
2. Check WHOIS for the domain's status and expiry date - look for "clientHold," "pendingDelete," or an expired date.
3. Verify the nameservers at your registrar match what Getwebup gave you. Run dig yourdomain.com NS +short.
4. If nameservers are correct, confirm the zone exists in cPanel/WHM and has an A record for both the root and www.
5. If you're using external DNS instead of Getwebup nameservers, check the A record there points to the correct IP with dig yourdomain.com A +short.

The fix

If nameservers just changed

Wait it out - but you don't have to wait blind. Use a propagation checker to see which regions have picked up the new nameservers. If it's been more than 48 hours and most regions still show the old servers, double-check you saved the change correctly at the registrar (some registrars require you to explicitly remove the "default nameservers" toggle before custom nameservers take effect).

If the zone or A record is missing

In cPanel, go to Domains and confirm the domain is listed with a green "active" status. If it's missing, add it as the primary or an addon domain. In WHM, go to DNS Zones, search for the domain, and confirm an A record exists for both yourdomain.com and www.yourdomain.com pointing to your server IP:

yourdomain.com.     A     14400     203.0.113.10
www.yourdomain.com. A     14400     203.0.113.10

If it's a local cache problem

Flush DNS on your own machine before assuming the server is broken:

# Windows
ipconfig /flushdns

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Linux (systemd-resolved)
sudo resolvectl flush-caches

Also try switching your resolver temporarily to 1.1.1.1 or 8.8.8.8 to rule out your ISP's DNS caching a stale answer.

If the domain is expired or on hold

Renew it at your registrar immediately. A domain in "pendingDelete" status can take days to release even after renewal, so don't let this one lapse twice.

Prevention

• Set calendar reminders for domain renewal 30 days out, and turn on auto-renew if your registrar supports it
• When migrating a domain to Getwebup, lower the TTL on old DNS records to 300 seconds a day or two before the cutover, so the change propagates faster
• Always add the domain in cPanel before or immediately after pointing nameservers, not days later
• Keep a record of both your registrar login and your DNS provider login - most NXDOMAIN panics happen when someone can't remember where the domain actually lives

When to open a support ticket

If dig confirms the nameservers are correct, the zone exists with the right A records, and it's been more than 48 hours since any change, that's when it's worth reaching out to your hosting provider's support team with the dig output attached. It saves a round of "have you tried flushing your DNS" and gets straight to checking server-side zone configuration.