RFC 9210: DNS Transport over TCP - Operational Requirements
In plain English — editorial summary, not part of the RFC
This document updates RFCs 1123 and 1536. This document requires the operational practice of permitting DNS messages to be carried over TCP on the Internet as a Best Current Practice. This operational requirement is aligned with the implementation requirements in RFC 7766. The use of TCP includes both DNS over unencrypted TCP as well as over an encrypted TLS session. The document also considers the consequences of this form of DNS communication and the potential operational issues that can arise when this Best Current Practice is not upheld.
Document record
- Document ID
- RFC9210
- Published
- March 2022
- Authors
- J. Kristoff; D. Wessels
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 29
- Also known as
- BCP235
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
- RFC 9224Finding the Authoritative Registration Data Access Protocol (RDAP) ServiceCurrent
March 2022
- RFC 9276Guidance for NSEC3 Parameter SettingsCurrent
August 2022
- RFC 9364DNS Security Extensions (DNSSEC)Current
February 2023
- RFC 8976Message Digest for DNS ZonesCurrent
February 2021
- RFC 9445RADIUS Extensions for DHCP-Configured ServicesCurrent
August 2023
- RFC 9520Negative Caching of DNS Resolution FailuresCurrent
December 2023
- RFC 9565An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information ElementCurrent
March 2024
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?