Initializing a DNS Resolver with Priming Queries
draft-klh-dnsop-rfc8109bis-01
Network Working Group P. Koch
Internet-Draft DENIC eG
Obsoletes: 8109 (if approved) M. Larson
Intended status: Best Current Practice P. Hoffman
Expires: 20 May 2021 ICANN
16 November 2020
Initializing a DNS Resolver with Priming Queries
draft-klh-dnsop-rfc8109bis-01
Abstract
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, when published, obsoletes RFC 8109.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 20 May 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Koch, et al. Expires 20 May 2021 [Page 1]
Internet-Draft DNS Priming Queries November 2020
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Changes from RFC 8109 . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Description of Priming . . . . . . . . . . . . . . . . . . . 4
2.1. Content of Priming Information . . . . . . . . . . . . . 4
3. Priming Queries . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Repeating Priming Queries . . . . . . . . . . . . . . . . 5
3.2. Target Selection . . . . . . . . . . . . . . . . . . . . 5
3.3. DNSSEC with Priming Queries . . . . . . . . . . . . . . . 6
4. Priming Responses . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Expected Properties of the Priming Response . . . . . . . 7
4.2. Completeness of the Response . . . . . . . . . . . . . . 7
5. Post-Priming Strategies . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
Recursive DNS resolvers need a starting point to resolve queries.
[RFC1034] describes a common scenario for recursive resolvers: they
begin with an empty cache and some configuration for finding the
names and addresses of the DNS root servers. [RFC1034] describes
that configuration as a list of servers that will give authoritative
answers to queries about the root. This has become a common
implementation choice for recursive resolvers, and is the topic of
this document.
This document describes the steps needed for this common
implementation choice. Note that this is not the only way to start a
recursive name server with an empty cache, but it is the only one
described in [RFC1034]. Some implementers have chosen other
directions, some of which work well and others of which fail
Koch, et al. Expires 20 May 2021 [Page 2]
Internet-Draft DNS Priming Queries November 2020
(sometimes disastrously) under different conditions. For example, an
Show full document text