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

Attach message metadata using OPT

01

OPT is a pseudo-record in the Additional section, not ordinary zone data.

Related RFCs and changes

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

RFC 6891 · § 6.1.1EXAMPLE
3 / 3
Attach message metadata using OPTOPT is a pseudo-record in the Additional section, not ordinary zone data.DNS QuestionAdditional sectionOPT · owner root · type 41message capabilities / optionsOne OPT per message; not ordinary authoritative record data
03
Interpret its fields as message capabilities, not an address record.

Interpret its fields as message capabilities, not an address record.

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

A message contains at most one OPT record.

  • A message contains at most one OPT record.
  • OPT has a root owner name, type 41, fixed metadata, and variable options.
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. Attach message metadata using OPT
  2. Advertise a UDP receive limit
  3. Separate EDNS version and response codes
  4. Parse extensible option tuples
  5. Keep OPT out of the record cache
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗