🌐
DNS Error
DNS Error: NXDOMAIN (Non-Existent Domain)
The DNS server successfully responded, but confirmed the requested domain name does not exist in DNS at all.
What This Error Means
NXDOMAIN is a specific, valid DNS response code meaning "this domain name does not exist" — it's not a network failure or timeout; the DNS server responded successfully and definitively said there is no such name in its records.
Why It Occurs
Most commonly a genuine typo in the domain name, a domain that was never registered or has expired, a subdomain that was never created in DNS, or DNS changes (like a new domain/subdomain) that haven't propagated yet.
Symptoms
- ⚠ Browsers show "This site can't be reached" / DNS_PROBE_FINISHED_NXDOMAIN
- ⚠ `nslookup` or `dig` explicitly return "NXDOMAIN" in their output
Common Causes
- • Typo in the domain name being requested
- • The domain was never registered, or its registration expired
- • A subdomain record was never created in the DNS zone
- • Recently created DNS record hasn't propagated to the resolver being used yet
How to Fix It
- Double-check the exact spelling of the domain/subdomain being requested
- Query an authoritative or well-known public resolver directly to rule out a stale local cache: `dig example.com @8.8.8.8`
- If this is your own domain and you just created the record, DNS propagation can take anywhere from minutes to (rarely) 48 hours depending on TTL — check the record's TTL and wait accordingly
- Verify the domain registration is actually active and hasn't expired, via a WHOIS lookup
- If it's a subdomain, confirm the record actually exists in your DNS provider's dashboard for that exact subdomain
| Command | Purpose |
|---|---|
| dig example.com @8.8.8.8 | Query a specific public resolver directly, bypassing any local DNS cache |
| nslookup example.com | Basic DNS lookup to confirm resolution status |
Advertisement
Verification
- ✓ `dig`/`nslookup` against multiple resolvers (e.g. 8.8.8.8 and 1.1.1.1) both return a valid answer instead of NXDOMAIN
Prevention
- → Set reasonable TTLs on DNS records so future changes propagate at a predictable, appropriate speed
- → Set domain renewal auto-renewal and expiry alerts to avoid accidental lapses