Requirements for a Mechanism Identifying a Name Server Instance
RFC 4892, “Requirements for a Mechanism Identifying a Name Server Instance”, is an Informational document published in June 2007 by S. Woolf, D. Conrad. 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. A standardized mechanism to determine the identity of a name server responding to a particular query would be useful, particularly as a diagnostic aid for administrators. Existing ad hoc mechanisms for addressing this need have some shortcomings, not the least of which is the lack of prior analysis of exactly how such a mechanism should be designed and deployed. This document describes the existing convention used in some widely deployed implementations of the DNS protocol, including advantages and disadvantages, and discusses some attributes of an improved mechanism. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 4892 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4891 Using IPsec to Secure IPv6-in-IPv4 Tunnels
- RFC 4893 BGP Support for Four-octet AS Number Space
- RFC 4890 Recommendations for Filtering ICMPv6 Messages in Firewalls
- RFC 4894 Use of Hash Algorithms in Internet Key Exchange and IPsec
- RFC 4889 Network Mobility Route Optimization Solution Space Analysis
- RFC 4895 Authenticated Chunks for the Stream Control Transmission Protocol
- RFC 4888 Network Mobility Route Optimization Problem Statement
- RFC 4896 Signaling Compression Corrections and Clarifications