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.
[1]
Paul V. Mockapetris,et al.
Domain names - implementation and specification
,
1987,
RFC.
[2]
Rob Austein,et al.
DNS Name Server Identifier (NSID) Option
,
2007,
RFC.
[3]
Scott Rose,et al.
DNS Security Introduction and Requirements
,
2005,
RFC.
[4]
Scott Rose,et al.
DNS Security Introduction and Requirements
,
2005,
RFC.
[5]
Paul V. Mockapetris,et al.
Domain names: Concepts and facilities
,
1983,
RFC.
[6]
Ted Hardie,et al.
Distributing Authoritative Name Servers via Shared Unicast Addresses
,
2002,
RFC.