Visual RFC.
ALL RFCs / RFC 1035
Read the RFC ↗
RFC 1035 / PROTOCOL MECHANISMS

Switch transport when a response is truncated

04

Original DNS uses UDP and TCP on server port 53. TCP messages have a two-octet length prefix.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 4.2 ↗
RFC 1035 · § 4.2EXAMPLE
3 / 3
Switch transport when a response is truncatedOriginal DNS uses UDP and TCP on server port 53. TCP messages have a two-octet length prefix.Response larger than original UDP limitOriginal UDP envelope: 512 octetsTC = 1 · truncatedlengthcomplete DNS message via TCPEDNS later extends UDP signaling; TCP has a two-byte length
03
A TCP exchange carries a length-prefixed complete message.

A TCP exchange carries a length-prefixed complete message.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 1035 · 512-byte UDP baselineRFC 6891 § 4.3

EDNS allows a requester to advertise a larger UDP payload size; it is not a universal fixed larger limit.

Read the updated RFC section ↗
KEY POINT

The original UDP message limit is 512 octets; TC indicates truncation.

  • The original UDP message limit is 512 octets; TC indicates truncation.
  • Later EDNS signaling can support larger UDP responses; that does not remove path-MTU constraints.
DETAILS

The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Read a DNS message envelope
  2. Encode labels and records
  3. Compress a repeated name suffix
  4. Switch transport when a response is truncated
  5. Load an authoritative zone file
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗