Visual RFC.
ALL RFCs / RFC 1034
Read the RFC ↗
RFC 1034 / AUTHORITY

Delegation & glue

03

A parent zone points toward the servers responsible for a child. Address glue can make that referral reachable.

Related RFCs and changes

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

RFC 1034 · § 4.2.1EXAMPLE
4 / 4
Delegation & glueParent referral and address glue are visibly separate from the child authoritative zone.PARENT ZONE: org.example.org. NSns.example.org.ZONE CUTCHILD: example.org.SOA · NS · www Aauthoritative child dataGLUE192.0.2.53server addressreach serverThe resolver can now contact the child’s server
04
Continue at the delegated authority.

The resolver uses the referral to get closer to the answer.

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

Delegation divides responsibility.

  • NS records mark a delegation at the lower boundary of a parent zone.
  • The child zone contains its own authoritative data, including its apex SOA and NS records.
  • Glue supplies necessary server addresses when finding those addresses would otherwise require first reaching the delegated zone.
DETAILS

A domain and a zone are different: the org domain contains example.org, but the org zone need not contain its delegated authoritative records.

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 ↗