DNS errors9 min read

How to Fix DNS SERVFAIL Errors

SERVFAIL means a recursive resolver could not produce a trustworthy answer. Unlike NXDOMAIN, it does not mean the hostname is missing. The fastest fix comes from identifying which stage of resolution failed.

Quick answer

SERVFAIL is not a normal missing-record response. It means the resolver failed while resolving or validating the DNS answer. The fastest path is to compare public resolvers, trace delegation, check authoritative nameservers and inspect DNSSEC records if validating resolvers are affected.

Diagnostic checklist

  • Confirm whether SERVFAIL appears on one resolver or many.
  • Use dig +trace to find delegation breaks.
  • Compare SOA serials across authoritative nameservers.
  • Check whether a stale DS record remains at the registrar.
  • Avoid repeated DNS changes until you know whether the failure is cached or authoritative.

Useful next checks

Reproduce the failure with several resolvers

Compare validating resolversdig
dig @1.1.1.1 example.com A
dig @8.8.8.8 example.com A
dig @9.9.9.9 example.com A

Trace the delegation

A trace follows the path from the root to the authoritative zone. Look for missing glue, unreachable nameservers, timeouts or a delegation that points to the wrong provider.

Delegation tracedig
dig +trace example.com A
dig example.com NS +trace

Test authoritative servers directly

Authoritative reachability and consistencydig
dig @ns1.example.net example.com A +norecurse
dig @ns2.example.net example.com A +norecurse
dig @ns1.example.net example.com SOA +short
dig @ns2.example.net example.com SOA +short

Validate DNSSEC

If the failure affects validating resolvers, inspect the DS record at the parent and DNSKEY/RRSIG records in the child zone. A stale DS after changing DNS providers is a frequent cause.

DNSSEC checksdig
dig example.com DS +dnssec
dig example.com DNSKEY +dnssec
dig example.com A +dnssec +cdflag

Frequent root causes

Nameserver unreachable over UDP or TCP 53

Check firewall rules, routing and both DNS transports.

Lame delegation

Every delegated server must answer authoritatively for the zone.

Stale DS record

Update or remove the DS at the registrar to match the active DNSKEY.

Expired DNSSEC signatures

Restore signing and publish valid RRSIG records.

Different zone versions

Synchronise authoritative servers and compare SOA serials.

Related DNS guides