Delegation Revalidation by DNS Resolvers
draft-ietf-dnsop-ns-revalidation-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Shumon Huque , Paul A. Vixie , Ralph Dolmans | ||
Last updated | 2021-03-12 (Latest revision 2020-09-08) | ||
Replaces | draft-huque-dnsop-ns-revalidation | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
DNSDIR Early review
(of
-04)
by R. Gieben
On the right track
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
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:
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
Paul A. Vixie
Ralph Dolmans
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)