DNS Name Server Identifier Option
RFC 5001, “DNS Name Server Identifier Option”, is a Proposed Standard document published in August 2007 by R. Austein. The canonical text is published by the RFC Editor.
Abstract
With the increased use of DNS anycast, load balancing, and other mechanisms allowing more than one DNS name server to share a single IP address, it is sometimes difficult to tell which of a pool of name servers has answered a particular query. While existing ad-hoc mechanisms allow an operator to send follow-up queries when it is necessary to debug such a configuration, the only completely reliable way to obtain the identity of the name server that responded is to have the name server include this information in the response itself. This note defines a protocol extension to support this functionality. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5001 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5002 The Session Initiation Protocol P-Profile-Key Private Header
- RFC 5003 Attachment Individual Identifier Types for Aggregation
- RFC 4998 Evidence Record Syntax
- RFC 5004 Avoid BGP Best Path Transitions from One External to Another
- RFC 4997 Formal Notation for RObust Header Compression
- RFC 5005 Feed Paging and Archiving
- RFC 4996 RObust Header Compression : A Profile for TCP/IP
- RFC 5006 IPv6 Router Advertisement Option for DNS Configuration