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

Load an authoritative zone file

05

Master files express records with origins, TTLs, classes, types, and data.

Related RFCs and changes

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

DIAGRAM§ 5.1 ↗
RFC 1035 · § 5.1EXAMPLE
3 / 3
Load an authoritative zone fileMaster files express records with origins, TTLs, classes, types, and data.MASTER FILE$ORIGIN example.org.www 300 IN A 192.0.2.20load zonewww.example.org. A 192.0.2.20Authoritative data, not a resolver cache entryRelative names use origin; omitted owners can inherit
03
Load the resulting records as authoritative zone data.

Load the resulting records as authoritative zone data.

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

Relative names use an origin; omitted owners can inherit from the previous record.

  • Relative names use an origin; omitted owners can inherit from the previous record.
  • The original master-file syntax is supplemented by later specifications; use current TTL directives correctly.
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 ↗