Visual RFC.
ALL RFCs / RFC 1034
Read the RFC ↗
RFC 1034 / NAMES & RECORDS

Resource records

02

DNS stores typed records, not simply a table of names and IP addresses.

Related RFCs and changes

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

DIAGRAM§ 3.6 ↗
RFC 1034 · § 3.6EXAMPLE
4 / 4
Resource recordsA typed query selects an MX row and then reveals a useful address record.Question: example.org.QTYPE = MX · QCLASS = INOWNERTYPEDATAexample.org.MX10 mail.example.org.mail.example.org.A192.0.2.20example.org.NSns.example.org.separate mail deliveryUse the discovered mail service
04
Use the discovered service.

Delivering email is a separate application protocol.

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

Ask for the record type you need.

  • A record has an owner, type, class, TTL, and type-specific data.
  • A records map names to IPv4 addresses; MX identifies mail exchangers; NS identifies name servers.
  • Question, Answer, Authority, and Additional are distinct message sections.
DETAILS

The Additional section can save a later lookup, but is supporting information rather than a replacement for the answer.

Read the RFC section ↗

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

Privacy
All chapters in this RFC
  1. The name tree
  2. Resource records
  3. Delegation & glue
  4. Iterative resolution
  5. Recursive resolution
  6. Caches & TTL
  7. Aliases
  8. Missing names & failures
  9. Wildcard synthesis
  10. Zone maintenance
  11. Reverse lookups
  12. Transport & historical scope

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 ↗