RFC 9715: IP Fragmentation Avoidance in DNS over UDP
In plain English — editorial summary, not part of the RFC
The widely deployed Extension Mechanisms for DNS (EDNS(0)) feature in the DNS enables a DNS receiver to indicate its received UDP message size capacity, which supports the sending of large UDP responses by a DNS server. Large DNS/UDP messages are more likely to be fragmented, and IP fragmentation has exposed weaknesses in application protocols. It is possible to avoid IP fragmentation in DNS by limiting the response size where possible and signaling the need to upgrade from UDP to TCP transport where necessary. This document describes techniques to avoid IP fragmentation in DNS.
Document record
- Document ID
- RFC9715
- Published
- January 2025
- Authors
- K. Fujiwara; P. Vixie
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9726Operational Considerations for Use of DNS in Internet of Things (IoT) DevicesCurrent
March 2025
- RFC 9803Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) ValuesCurrent
June 2025
- RFC 9824Compact Denial of Existence in DNSSECCurrent
September 2025
- RFC 9904DNSSEC Cryptographic Algorithm Recommendation Update ProcessCurrent
November 2025
- RFC 9905Deprecating the Use of SHA-1 in DNSSEC Signature AlgorithmsCurrent
November 2025
- RFC 9906Deprecate Usage of ECC-GOST within DNSSECCurrent
November 2025
- RFC 9520Negative Caching of DNS Resolution FailuresCurrent
December 2023
- RFC 9445RADIUS Extensions for DHCP-Configured ServicesCurrent
August 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?