| CARVIEW |
Select Language
HTTP/2 200
date: Wed, 16 Jul 2025 12:15:51 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 96016d639f8aff60-BOM
alt-svc: h3=":443"; ma=86400
Information on RFC 7766 » RFC Editor
Search RFCs
RFC 7766
DNS Transport over TCP - Implementation Requirements, March 2016
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 5966
- Updates:
- RFC 1035, RFC 1123
- Updated by:
- RFC 8490, RFC 9103
- Authors:
- J. Dickinson
S. Dickinson
R. Bellis
A. Mankin
D. Wessels - Stream:
- IETF
- Source:
- dnsop (ops)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7766
Discuss this RFC: Send questions or comments to the mailing list dnsop@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7766
Abstract
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us