Skip to main content

Delegation Revalidation by DNS Resolvers

Document Type Replaced Internet-Draft (dnsop WG)
Expired & archived
Authors Shumon Huque , Paul A. Vixie , Ralph Dolmans
Last updated 2020-06-09 (Latest revision 2020-03-09)
Replaced by draft-ietf-dnsop-ns-revalidation
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-dnsop-ns-revalidation
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Shumon Huque
Paul A. Vixie
Ralph Dolmans

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