RFC 9103: DNS Zone Transfer over TLS
In plain English — editorial summary, not part of the RFC
DNS zone transfers are transmitted in cleartext, which gives attackers the opportunity to collect the content of a zone by eavesdropping on network connections. The DNS Transaction Signature (TSIG) mechanism is specified to restrict direct zone transfer to authorized clients only, but it does not add confidentiality. This document specifies the use of TLS, rather than cleartext, to prevent zone content collection via passive monitoring of zone transfers: XFR over TLS (XoT). Additionally, this specification updates RFC 1995 and RFC 5936 with respect to efficient use of TCP connections and RFC 7766 with respect to the recommended number of connections between a client and server for each transport.
Document record
- Document ID
- RFC9103
- Published
- August 2021
- Authors
- W. Toorop; S. Dickinson; S. Sahib; P. Aras; A. Mankin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 7553The Uniform Resource Identifier (URI) DNS Resource RecordCurrent
June 2015
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 9076DNS Privacy ConsiderationsCurrent
July 2021
- RFC 8981Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6Current
February 2021
- RFC 9250DNS over Dedicated QUIC ConnectionsCurrent
May 2022
- RFC 8932Recommendations for DNS Privacy Service OperatorsCurrent
October 2020
- RFC 8765DNS Push NotificationsCurrent
June 2020
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?