Delegation Revalidation by DNS Resolvers
draft-huque-dnsop-ns-revalidation-01

Document Type Replaced Internet-Draft (dnsop WG)
Authors Shumon Huque  , Paul Vixie  , Ralph Dolmans 
Last updated 2020-06-09 (latest revision 2020-03-09)
Replaced by draft-ietf-dnsop-ns-revalidation
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-dnsop-ns-revalidation
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-huque-dnsop-ns-revalidation-01.txt

Abstract

This document recommends improved DNS [RFC1034] [RFC1035] resolver behavior with respect to the processing of Name Server (NS) resource record sets (RRset) during iterative resolution. When following a referral response from an authoritative server to a child zone, DNS resolvers should explicitly query the authoritative NS RRset at the apex of the child zone and cache this in preference to the NS RRset on the parent side of the zone cut. Resolvers should also periodically revalidate the child delegation by re-quering the parent zone at the expiration of the TTL of the parent side NS RRset.

Authors

Shumon Huque (shuque@gmail.com)
Paul Vixie (paul@redbarn.org)
Ralph Dolmans (ralph@NLnetLabs.nl)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)