Glue In DNS Referral Responses Is Not Optional
draft-andrews-dnsop-glue-is-not-optional-01
Document | Type |
Replaced Internet-Draft
(dnsop WG)
Expired & archived
|
|
---|---|---|---|
Author | Mark P. Andrews | ||
Last updated | 2020-06-03 (Latest revision 2020-04-16) | ||
Replaced by | draft-ietf-dnsop-glue-is-not-optional | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-dnsop-glue-is-not-optional | |
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
The DNS uses glue records to allow iterative clients to find the addresses of nameservers that live within the delegated zone. Glue records are expected to be returned as part of a referral and if they cannot be fitted into the UDP response, TC=1 MUST be set to inform the client that the response is incomplete and that TCP SHOULD be used to retrieve the full response.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)