EDNS0 (Extension Mechanism for DNS)
What is EDNS0 (Extension Mechanism for DNS)?
EDNS0 (RFC 6891) extends DNS with an optional OPT record so resolvers can signal larger payload sizes and other capabilities the original 1987 protocol never anticipated, including DNS Cookies (RFC 7873) and padding. AdminKit's DNS lookup tool sends EDNS0-aware queries so it can retrieve full DNSSEC and large-answer responses correctly.
By AdminKit team, Netbase JSC · Updated
EDNS0 (RFC 6891) extends the original DNS message format with an optional pseudo-record, OPT, that lets a resolver advertise capabilities the 1987-era protocol never anticipated. Its most immediate job is signaling a larger UDP payload size than the original 512-byte limit, which is what lets DNS carry the bigger answers DNSSEC-signed zones produce without falling back to TCP for every query. EDNS0’s extensible options field is also how later additions, like the DNSSEC OK (DO) bit and DNS Cookies (RFC 7873), attach to a query without changing the core wire format again — each one assigned its own option code in IANA’s DNS Parameters registry. A resolver or server that doesn’t understand EDNS0 simply ignores the OPT record and responds as if it weren’t there, which is why support rolled out gradually without breaking older infrastructure. The advertised payload size still matters: DNS Flag Day 2020, a community effort by DNS software and service providers, recommended a default EDNS buffer size of 1232 bytes so large UDP answers avoid IP fragmentation, with servers switching to TCP when a response doesn’t fit. ISC’s EDNS Compliance testing tracks a related problem: improper EDNS handling holds back new DNS features, and DNS Cookies in particular require unknown EDNS options to be handled correctly by all servers. AdminKit’s DNS lookup tool sends EDNS0-aware queries so it can retrieve full DNSSEC and large-answer responses correctly. See the DNS cookies entry for how that particular EDNS0 option authenticates a query/response pair without a full TCP handshake. Another option built the same way, EDNS Client Subnet (RFC 7871), lets a resolver forward part of the original client’s address for geo-steering, at some cost to that client’s privacy. A third option, EDNS(0) Padding (RFC 7830), pads a query or response out to a fixed size so its length alone doesn’t leak which domain is being looked up to an observer watching otherwise-encrypted DNS traffic.
EDNS0 (Extension Mechanism for DNS) is part of AdminKit’s DNS cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What problem does EDNS0 solve that the original DNS message format couldn't?
It lets a resolver signal a larger UDP payload size than the original 512-byte limit, which is what lets DNS carry the bigger answers DNSSEC-signed zones produce without falling back to TCP for every query.
What happens when a resolver or server doesn't support EDNS0?
It simply ignores the OPT pseudo-record and responds as if EDNS0 weren't there, which is why support rolled out gradually without breaking older infrastructure.
What later DNS options are built on EDNS0's extension mechanism?
DNS Cookies (RFC 7873), EDNS Client Subnet (RFC 7871) and EDNS(0) Padding (RFC 7830) all attach to a query as EDNS0 options rather than changing the core DNS wire format.