RFC 7766: DNS Transport over TCP - Implementation Requirements
In plain English — editorial summary, not part of the RFC
This document specifies the requirement for support of TCP as a transport protocol for DNS implementations and provides guidelines towards DNS-over-TCP performance on par with that of DNS-over-UDP. This document obsoletes RFC 5966 and therefore updates RFC 1035 and RFC 1123.
Document record
- Document ID
- RFC7766
- Published
- March 2016
- Authors
- J. Dickinson; S. Dickinson; R. Bellis; A. Mankin; D. Wessels
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 19
- Also known as
- —
- Obsoletes:
- RFC 5966
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7828The edns-tcp-keepalive EDNS0 OptionCurrent
April 2016
- RFC 8310Usage Profiles for DNS over TLS and DNS over DTLSCurrent
March 2018
- RFC 7646Definition and Use of DNSSEC Negative Trust AnchorsCurrent
September 2015
- RFC 7535AS112 Redirection Using DNAMECurrent
May 2015
- RFC 7534AS112 Nameserver OperationsCurrent
May 2015
- RFC 8027DNSSEC Roadblock AvoidanceCurrent
November 2016
- RFC 8145Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)Updated
April 2017
- RFC 7344Automating DNSSEC Delegation Trust MaintenanceUpdated
September 2014
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?