RFC 7706: Decreasing Access Time to Root Servers by Running One on Loopback
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8806.
Current version: 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. Some DNS recursive resolver operators want to prevent snooping of requests sent to DNS root servers by third parties. Such resolvers can greatly decrease the round-trip time and prevent observation of requests by running a copy of the full root zone on a loopback address (such as 127.0.0.1). This document shows how to start and maintain such a copy of the root zone that does not pose a threat to other users of the DNS, at the cost of adding some operational fragility for the operator.
Document record
- Document ID
- RFC7706
- Published
- November 2015
- Authors
- W. Kumari; P. Hoffman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 12
- Also known as
- —
- Obsoleted by:
- RFC 8806
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 7707Network Reconnaissance in IPv6 NetworksCurrent
March 2016
- RFC 7717IKEv2-Derived Shared Secret Key for the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)Current
December 2015
- RFC 7718Registries for the One-Way Active Measurement Protocol (OWAMP)Current
December 2015
- RFC 7719DNS TerminologyObsoleted
December 2015
- RFC 7690Close Encounters of the ICMP Type 2 Kind (Near Misses with ICMPv6 Packet Too Big (PTB))Current
January 2016
- RFC 7686The ".onion" Special-Use Domain NameCurrent
October 2015
- RFC 7683Diameter Overload Indication ConveyanceUpdated
October 2015
- RFC 7682Considerations for Internet Routing Registries (IRRs) and Routing Policy ConfigurationCurrent
December 2015
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?