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

Compress a repeated name suffix

03

A pointer can replace a previously occurring name or suffix within the same DNS message.

Related RFCs and changes

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

RFC 1035 · § 4.1.4EXAMPLE
3 / 3
Compress a repeated name suffixA pointer can replace a previously occurring name or suffix within the same DNS message.ONE DNS MESSAGEoffset 20: 7 example 3 org 03 www11 + offset 20A pointer replaces the repeated suffixThe 14-bit pointer offset is within this DNS message
03
A pointer refers back to the existing example.org suffix.

A pointer refers back to the existing example.org suffix.

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

A compression pointer uses the top two bits 11 and a 14-bit message offset.

  • A compression pointer uses the top two bits 11 and a 14-bit message offset.
  • Parsing must remain bounded; a malformed pointer must not cause unbounded traversal.
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

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗