Skip to main content

Glue In DNS Referral Responses Is Not Optional
draft-ietf-dnsop-glue-is-not-optional-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Author Mark P. Andrews
Last updated 2020-12-05 (Latest revision 2020-06-03)
Replaces draft-andrews-dnsop-glue-is-not-optional
RFC stream Internet Engineering Task Force (IETF)
Formats
Reviews
OPSDIR Last Call Review Incomplete, due 2023-05-10
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

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

Mark P. Andrews

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