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

Recursive resolution

05

A stub client asks a recursive service to return the final answer or an error instead of forwarding referrals to the user.

Related RFCs and changes

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

RFC 1034 · § 4.3.1EXAMPLE
4 / 4
Recursive resolutionThe client makes one request while the recursive resolver performs the authority traversal.Stub clientone requestRecursive resolverchases the answerRD = 1Rootorg.example.org.Final answerThe client receives an answer, not a referral chain
04
Return a completed result.

The stub does not need to chase the referral chain.

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

Recursion is a service, not an obligation.

  • RD requests recursion; RA indicates whether the server offers recursive service.
  • A server may decline recursion for a particular client.
  • A recursive response contains an answer or error, rather than merely a referral.
DETAILS

The stub and recursive resolver are roles. A deployment may combine functions, and an authoritative server need not offer recursion.

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 ↗