SERVFAIL means the resolver tried and failed: not “this name does not exist”, but “I could not get a trustworthy answer”. The three usual reasons are broken DNSSEC, nameservers that do not answer or refuse, and a broken delegation. Each has a quick test.
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4242
How 6 other clients word the same error
nslookup
** server can't find example.com: SERVFAIL
host
Host example.com not found: 2(SERVFAIL)
Windows nslookup
*** dns.google can't find example.com: Server failed
Windows PowerShell
example.com : DNS server failure.
Node.js
Error: queryA ESERVFAIL example.com
systemd-resolved
resolve call failed: Could not resolve 'example.com', server or network returned error: SERVFAIL
| Error | SERVFAIL |
| Usually fixed by | The domain owner |
| RCODE | 2 — Server Failure (RFC 1035) |
| Most common causes | DNSSEC, unreachable or refusing nameservers, broken delegation |
| Cached for | Seconds to at most 5 minutes (RFC 9520) |
Look up the domain’s DNS
Enter the domain: we ask its nameservers for every common record, from outside your network, and say whether DNSSEC validates.
What it means
A resolver answers SERVFAIL when it cannot produce an answer it can vouch for. From an authoritative server it means the server has no valid data for the zone; from a resolver it covers many conditions — which is why the extended error (EDE) line many resolvers now add is the best clue.
Resolvers cache a failure only briefly — from a second up to five minutes — so once the cause is fixed, SERVFAIL clears quickly.
Why it happens
- DNSSEC validation failed: a DS record at the registrar that matches no key in the zone, or expired signatures — see DNSSEC failure.
- Every nameserver for the domain timed out, was unreachable or refused — see REFUSED and lame delegation.
- A broken delegation: nameservers at the registrar that differ from the ones actually serving the zone, or a delegation loop.
- A CNAME loop, or a secondary nameserver whose copy of the zone expired.
How to fix it
- Read the extended error: dig shows an “EDE:” line from resolvers such as 1.1.1.1 and 8.8.8.8 — DNSSEC Bogus, DNSKEY Missing and No Reachable Authority each point at a different fix.
- Repeat the query with +cd (checking disabled). If it works with +cd and fails without, the problem is DNSSEC.
- Query each of the domain’s nameservers directly with +norecurse: each should answer with the aa flag. A timeout or REFUSED names the broken server.
- Fix at the source: the DS record at the registrar, the zone at the DNS host, or the nameserver list at the registrar.
See it for yourself
dig example.com A @1.1.1.1
dig example.com A @1.1.1.1 +cd
dig example.com A @ns1.example-dns.net +norecurse
The first shows the EDE reason; the second tests whether DNSSEC is to blame; the third asks one nameserver directly.
Questions
Why does the domain work on one network and fail with SERVFAIL on another?
Because only validating resolvers reject a broken DNSSEC signature: 1.1.1.1, 8.8.8.8 and Quad9 validate, some ISP resolvers do not. A domain that only fails on validating resolvers has a DNSSEC problem.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 9520 — rfc-editor.org
- RFC 2308 — rfc-editor.org
- Domain Troubleshooting — developers.google.com
- DNSSEC Guide — bind9.readthedocs.io
- Extended DNS error codes — developers.cloudflare.com