Viewing source data: draft-kh-dnsop-7706bis indexed from relaton-data-ids draft-kh-dnsop-7706bis
docid.type Internet-Draft
docid.primary True
relation.type includes
relation.bibitem.formattedref.content draft-kh-dnsop-7706bis-00
relation.bibitem.formattedref.format text/plain draft-kh-dnsop-7706bis-00
relation.bibitem.docid.type Internet-Draft
relation.bibitem.docid.primary True draft-kh-dnsop-7706bis-00
relation#2.type includes
relation#2.bibitem.formattedref.content draft-kh-dnsop-7706bis-01
relation#2.bibitem.formattedref.format text/plain draft-kh-dnsop-7706bis-01
relation#2.bibitem.docid.type Internet-Draft
relation#2.bibitem.docid.primary True draft-kh-dnsop-7706bis-01
title.content Decreasing Access Time to Root Servers by Running One On The Same Server
title.format text/plain
title.script Latn
title.language en
abstract.content <p>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 the same server, such as on a loopback address. 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. This draft will update RFC 7706. See Section 1.1 for a list of topics that will be added in the update. [ Ed note: Text inside square brackets ([]) is additional background information, answers to freqently asked questions, general musings, etc. They will be removed before publication.] [ This document is being collaborated on in Github at: The most recent version of the document, open issues, and so on should all be available there. The authors gratefully accept pull requests. ]</p>
abstract.format text/html
abstract.script Latn
abstract.language en
id draft-kh-dnsop-7706bis