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. This document obsoletes RFC 8109.
Document record
- Document ID
- RFC9609
- Published
- February 2025
- Authors
- P. Koch; M. Larson; P. Hoffman
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- BCP209
- Obsoletes:
- RFC 8109
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9615Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's OperatorCurrent
July 2024
- RFC 9617A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM)Current
August 2024
- RFC 9619In the DNS, QDCOUNT Is (Usually) OneCurrent
July 2024
- RFC 9589On the Use of the Cryptographic Message Syntax (CMS) Signing-Time Attribute in Resource Public Key Infrastructure (RPKI) Signed ObjectsCurrent
May 2024
- RFC 9630Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM)Current
August 2024
- RFC 9632Finding and Using Geofeed DataCurrent
August 2024
- RFC 9582A Profile for Route Origin Authorizations (ROAs)Current
May 2024
- RFC 9637Expanding the IPv6 Documentation SpaceCurrent
August 2024
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?