RFC 8806: Running a Root Server Local to a Resolver
In plain English — editorial summary, not part of the RFC
Some DNS recursive resolvers have longer-than-desired round-trip times to the closest DNS root server; those resolvers may have difficulty getting responses from the root servers, such as during a network attack. Some DNS recursive resolver operators want to prevent snooping by third parties of requests sent to DNS root servers. In both cases, resolvers can greatly decrease the round-trip time and prevent observation of requests by serving a copy of the full root zone on the same server, such as on a loopback address or in the resolver software. This document shows how to start and maintain such a copy of the root zone that does not cause problems for other users of the DNS, at the cost of adding some operational fragility for the operator. This document obsoletes RFC 7706.
Document record
- Document ID
- RFC8806
- Published
- June 2020
- Authors
- W. Kumari; P. Hoffman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 12
- Also known as
- —
- Obsoletes:
- RFC 7706
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8767Serving Stale Data to Improve DNS ResiliencyCurrent
March 2020
- RFC 8749Moving DNSSEC Lookaside Validation (DLV) to Historic StatusCurrent
March 2020
- RFC 8976Message Digest for DNS ZonesCurrent
February 2021
- RFC 8618Compacted-DNS (C-DNS): A Format for DNS Packet CaptureCurrent
September 2019
- RFC 8553DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node NamesCurrent
March 2019
- RFC 8552Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute LeavesCurrent
March 2019
- RFC 8509A Root Key Trust Anchor Sentinel for DNSSECCurrent
December 2018
- RFC 8482Providing Minimal-Sized Responses to DNS Queries That Have QTYPE=ANYCurrent
January 2019
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?