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

Iterative resolution

04

A resolver can do the chasing itself, choosing progressively closer servers until it finds an answer.

Related RFCs and changes

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

RFC 1034 · § 5.3.3EXAMPLE
4 / 4
Iterative resolutionOne resolver follows three progressively closer authorities.Resolverdoes the workRoot.TLDorg.Authorityexample.org.1 · query root2 · org referral3 · query orgchild referral4 · query childAnswer: www.example.org. A 192.0.2.20
04
Reach the answer.

The authoritative server returns the matching host record.

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

Each referral narrows the search.

  • Start with useful cached information or a configured server safety belt.
  • Choose servers with the closest known matching ancestor of the queried name.
  • Retry alternatives and bound the work so failure or alias loops do not run forever.
DETAILS

Real resolution may require extra address lookups and retries. These four steps illustrate a successful cold-cache path.

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 ↗