"Domain Not Found" DNS Errors: Causes and Fixes

Introduction

A “domain not found” error usually means the browser, application or resolver could not translate the domain name into a usable destination. In DNS terms, this often appears as NXDOMAIN, SERVFAIL, or a browser message such as DNS_PROBE_FINISHED_NXDOMAIN.

The cause may be a typo, expired domain, missing DNS zone, wrong nameserver delegation, deleted record, DNSSEC validation failure, or a registrar suspension. Checking WHOIS, nameservers and authoritative DNS together helps separate registration problems from DNS configuration problems.

Quick answer

Domain not found errors

“Domain not found” can mean different things depending on the layer that failed.

Why this matters

Quick diagnosis prevents wasted effort. Changing A records will not help if the domain expired or nameservers point to an empty zone.

How to check

Use DNS Lookup, WHOIS Lookup, Domain Expiry Checker and command-line tools to inspect registration and resolution status.

1. Spelling — Confirm the exact domain, subdomain and TLD.
2. WHOIS status — Check registration, expiry, registrar lock and lifecycle state.
3. Nameserver delegation — Verify NS records at the registrar.
4. Authoritative zone — Confirm the active DNS provider hosts the zone.
5. Required record — Check A, AAAA or CNAME for the hostname being accessed.
6. DNSSEC — Review DS records and DNSSEC status if validating resolvers fail.
7. External resolver test — Compare answers from multiple public resolvers.

Common problems

How to fix domain not found errors

1. Step 1: Confirm the exact hostname

   Check spelling, subdomain and TLD before investigating DNS.

2. Step 2: Run WHOIS and expiry checks

   Verify the domain is registered, active and not expired or suspended.

3. Step 3: Check nameserver delegation

   Confirm NS records point to the provider hosting the live zone.

4. Step 4: Query authoritative DNS

   Use dig @nameserver to see whether the zone and record exist.

5. Step 5: Add or restore missing records

   Create A, AAAA, CNAME or MX records required for the service.

6. Step 6: Review DNSSEC and DS records

   Fix broken DNSSEC before expecting validating resolvers to succeed.

7. Step 7: Renew or recover the domain if needed

   Restore registration before DNS changes can take effect publicly.

8. Step 8: Re-test from external resolvers

   Confirm the domain resolves from multiple public DNS servers.

Examples

dig example.com NS +noall +answer

whois example.com | egrep -i "Name Server|Registry Expiry|Domain Status"

dig +trace example.com A

dig @ns1.example-dns.net example.com A +noall +answer
dig @ns1.example-dns.net www.example.com A +noall +answer

dig app.example.com A

;; status: NXDOMAIN

Likely cause:
No A or CNAME record for app.example.com.

Fix:
Add app.example.com record in authoritative DNS.

whois example.com

Registry Expiry Date: 2024-01-10
dig example.com NS

;; status: NXDOMAIN

Likely cause:
Domain expired and zone was removed.

Fix:
Renew or recover domain at registrar first.

dig example.com NS +short
old-ns.hosting.example.

dig @old-ns.hosting.example example.com SOA

;; status: REFUSED or SERVFAIL

Likely cause:
Registrar still points to old/deleted DNS host.

Fix:
Update NS records to the active DNS provider.

Frequently asked questions