Topic · DNS & Infrastructure
DNS SERVFAIL
SERVFAIL means a DNS server was unable to complete a query successfully, without asserting the name does not exist.
How it works
Failures may arise from upstream resolution problems, DNSSEC validation, unreachable authorities or server errors.
What can go wrong
Repeated SERVFAIL during SPF, DKIM or DMARC lookups can interrupt legitimate authentication evaluation.
What to check or do
Compare validating and non-validating resolvers and inspect delegation, DNSSEC and authoritative server availability.
Practical scenario
A domain appears to have valid MX and SPF records on an internal recursive resolver, yet public validating resolvers return SERVFAIL. A stale DNSSEC DS record following a provider move is one possible explanation.
Verification checklist
- Repeat the exact DNS query on multiple validating resolvers.
- Compare behavior with authoritative answers and DNSSEC diagnostics.
- Inspect parent DS and child DNSKEY and RRSIG relationships.
- Repair the trust chain rather than disabling all email policy records.
How to investigate DNS SERVFAIL
- Signal to investigate
- An authoritative server returns valid-looking answers but validating resolvers fail.
- Evidence to collect
- Trace upstream resolution and check DNSSEC, transport timeouts and server errors.
- Common wrong conclusion
- SERVFAIL is not synonymous with nonexistence; do not delete records before diagnosing it.
How to interpret the evidence
SERVFAIL indicates that resolution failed, not that a queried record is absent. Causes may include an unresponsive authoritative nameserver, DNSSEC validation failure, transport problems or server-side errors. A scanner that labels SERVFAIL as missing SPF or DMARC can point an administrator toward the wrong fix.
What to change and how to verify it
Check response codes and DNSSEC validation independently. Compare authoritative answers and multiple resolving networks, then fix the failing dependency before editing the intended TXT content. Re-run the affected authentication lookup only after resolution succeeds consistently.
dig +dnssec example.com MXEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.