A SERVFAIL response is one of the least helpful things in DNS. It tells you something went wrong but not what, and for years the only way forward was to guess: is it a DNSSEC problem, an unreachable nameserver, a filtering policy, or a stale cache? Extended DNS Errors, or EDE, fix that by attaching a specific machine-readable reason to the failure. Instead of a bare SERVFAIL you can learn that the answer was DNSSEC bogus, or blocked by policy, or served stale because the upstream was unreachable. This guide explains what EDE is, how it rides along in the response, the codes you will meet most often, and how to read them with dig so a failure becomes a diagnosis.
Why a bare SERVFAIL is not enough
The classic DNS response code set is tiny. SERVFAIL, REFUSED, and NXDOMAIN cover enormous ranges of distinct problems with no detail. A validating resolver that rejects a zone because its signatures expired returns the same SERVFAIL as one that simply could not reach any authoritative server. For an operator that ambiguity turns every incident into a fishing expedition. Our general guide on reading a SERVFAIL still applies, but EDE is what turns that generic failure into a pointer at the actual cause.
How EDE travels in a response
EDE is defined in RFC 8914, published in October 2020. It is an EDNS0 option, option code 15, carried in the OPT pseudo-record of the response rather than in the main header. That placement matters: EDE does not replace the response code, it annotates it. A resolver still returns SERVFAIL in the header, and alongside it attaches an EDE option containing a 16-bit INFO-CODE identifying the reason, plus an optional human-readable EXTRA-TEXT field for extra context. Because it lives in the OPT record, EDE requires EDNS0 support on both ends, which modern resolvers and tools have. A response can even carry more than one EDE option when several things are wrong at once.
The codes you will meet most
IANA maintains the full registry of INFO-CODE values, and it keeps growing, but a handful account for most real-world failures. The table below groups the common ones by what they tell you to do next.
| Code | Meaning | What it points at |
|---|---|---|
| 6 | DNSSEC Bogus | Signatures present but invalid; a real validation failure to fix in the zone |
| 7 | Signature Expired | RRSIGs aged out; re-sign the zone |
| 8 | Signature Not Yet Valid | Clock skew or a signing window set in the future |
| 9 | DNSKEY Missing | No matching key for a signature in the chain |
| 10 | RRSIGs Missing | Records that should be signed are not |
| 3 | Stale Answer | Served from cache past TTL because upstream was unreachable |
| 15 | Blocked | Resolver policy blocked the name |
| 16 | Censored | Blocked by an external requirement |
| 17 | Filtered | Blocked at the operator's request |
| 18 | Prohibited | Resolver refuses to answer for this client |
| 22 | No Reachable Authority | Could not reach any authoritative server |
| 23 | Network Error | A network problem between resolver and authority |
The grouping is the useful part. Codes 5 through 12 are DNSSEC-related and point you at signing and key problems. Codes 15 through 18 mean something deliberately blocked the answer, which is policy, not breakage. Codes 22 and 23 are connectivity failures between the resolver and the authoritative servers. Code 3 means you are looking at a deliberately stale answer, which is a resilience feature rather than an error.
Reading EDE with dig
Recent versions of dig print the EDE option automatically when a response carries one, so you usually just have to look.
- Query the failing name, for example
dig +dnssec bad.example.com, and read the output rather than only the status line. - Look in the OPT pseudosection or the comments for a line beginning with EDE, such as
; EDE: 6 (DNSSEC Bogus). - Read any EXTRA-TEXT that follows the code; resolvers often add a short human-readable note naming the specific record or key at fault.
- Map the code to its category: a DNSSEC code sends you to your signer and keys, a block or filter code sends you to resolver policy, and a reachability code sends you to the authoritative servers.
- If one resolver gives a block code and another resolves fine, you are looking at policy on that resolver, not a problem with the domain.
How far to trust the error text
EDE text is informational and comes from whichever resolver answered, so treat the EXTRA-TEXT as a lead, not gospel, especially from a resolver you do not control. The numeric INFO-CODE is the reliable part; the free text is a convenience that an operator could word however they like. A resolver could even attach a misleading note, so when a code and its text seem to disagree, trust the code and confirm against a second resolver before you act. Remember too that EDE describes the view of the resolver that answered you; an authoritative server that is actually healthy can still be reported as unreachable by a resolver sitting behind a broken network path.
Frequently asked questions
Does EDE replace the SERVFAIL response code?
No. EDE annotates the existing response code rather than replacing it. The header still carries SERVFAIL, REFUSED, or NOERROR, and the EDE option in the OPT record adds the specific reason alongside it.
Why do I not see an EDE in my dig output?
Either the resolver does not populate EDE, the failure happened before an EDNS-aware response could be formed, or your dig is too old to print it. Use a current dig, query with +dnssec, and test a resolver known to emit extended errors.
What does EDE code 6 actually mean?
Code 6 is DNSSEC Bogus: signatures are present but validation failed, so the resolver refuses the answer. It signals a genuine problem in the zone's signing or chain of trust, not a transient glitch, and you fix it at the authoritative side.
Is an EDE block code a problem with my domain?
Usually not with the domain itself. Codes 15 through 18 mean a resolver's policy, or an external requirement, blocked the name. If the same name resolves on a different resolver, the block lives on that resolver, not in your zone.
Can a single response carry more than one EDE?
Yes. RFC 8914 allows multiple EDE options in one response, which a resolver uses when several issues apply at once. Read all of them, since together they can describe a compound failure more completely than any one code alone.
Extended DNS Errors turn the most frustrating response in DNS into an actionable one, pointing you straight at whether the trouble is signing, policy, or reachability. To run these queries and inspect the full response for a name, use the Valla DNS lookup tool, and keep our dig command cheat sheet and DNSSEC basics guide handy when a code sends you upstream.