RFC 9471: DNS Glue Requirements in Referral Responses
In plain English — editorial summary, not part of the RFC
The DNS uses glue records to allow iterative clients to find the addresses of name servers that are contained within a delegated zone. Authoritative servers are expected to return all available glue records for in-domain name servers in a referral response. If message size constraints prevent the inclusion of all glue records for in-domain name servers, the server must set the TC (Truncated) flag to inform the client that the response is incomplete and that the client should use another transport to retrieve the full response. This document updates RFC 1034 to clarify correct server behavior.
Document record
- Document ID
- RFC9471
- Published
- September 2023
- Authors
- M. Andrews; S. Huque; P. Wouters; D. Wessels
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 1034
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9472A YANG Data Model for Reporting Software Bills of Materials (SBOMs) and Vulnerability InformationCurrent
October 2023
- RFC 9476The .alt Special-Use Top-Level DomainCurrent
September 2023
- RFC 9460Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)Current
November 2023
- RFC 9486IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM)Current
September 2023
- RFC 9456Updates to the TLS Transport Model for SNMPCurrent
November 2023
- RFC 9455Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP PrefixesCurrent
August 2023
- RFC 9487Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)Current
November 2023
- RFC 9445RADIUS Extensions for DHCP-Configured ServicesCurrent
August 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?