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

Read a DNS message envelope

01

A DNS header carries transaction and control fields plus counts for four following sections.

Related RFCs and changes

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

RFC 1035 · § 4.1.1EXAMPLE
3 / 3
Read a DNS message envelopeA DNS header carries transaction and control fields plus counts for four following sections.ID / flags / QD / AN / NS / AR countsQuestion: name / type / classAnswer recordsAuthority recordsAdditional recordsHeader counts delimit sections; ID is not authentication
03
Use each count to locate the following record sections.

Use each count to locate the following record sections.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Question, Answer, Authority, and Additional are distinct sections.

  • Question, Answer, Authority, and Additional are distinct sections.
  • The ID helps correlate a response with its query; it is not cryptographic authentication.
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 ↗