RFC 8109: Initializing a DNS Resolver with Priming Queries
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9609.
Current version: RFC 9609 — Initializing a DNS Resolver with Priming Queries
In plain English — editorial summary, not part of the RFC
This document describes the queries that a DNS resolver should emit to initialize its cache. The result is that the resolver gets both a current NS Resource Record Set (RRset) for the root zone and the necessary address information for reaching the root servers.
Document record
- Document ID
- RFC8109
- Published
- March 2017
- Authors
- P. Koch; M. Larson; P. Hoffman
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 9609
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8078Managing DS Records from the Parent via CDS/CDNSKEYUpdated
March 2017
- RFC 8145Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)Updated
April 2017
- RFC 8072YANG Patch Media TypeCurrent
February 2017
- RFC 8071NETCONF Call Home and RESTCONF Call HomeCurrent
February 2017
- RFC 8063Key Relay Mapping for the Extensible Provisioning ProtocolCurrent
February 2017
- RFC 8161Benchmarking the Neighbor Discovery ProtocolCurrent
May 2017
- RFC 8056Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status MappingCurrent
January 2017
- RFC 8050Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format with BGP Additional Path ExtensionsCurrent
May 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?