API Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 4892
[ACTIVE]

Requirements for a Mechanism Identifying a Name Server Instance

Metadata

Publisher
IETF
Doc Type
Informational
Pages
8
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.
Publication Date
2007-06-01
Status Note
Informational
DOI
10.17487/RFC4892
Link
https://doi.org/10.17487/RFC4892
Author(s)
Suzanne Woolf
David R. Conrad
Keyword(s)
DNS, DNS Name Server
Latest version of IETF RFC 4892

Document Versions — IETF RFC 4892

  • ▶ IETF RFC 4892 (2007-06-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4892.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 4892, Requirements for a Mechanism Identifying a Name Server Instance. Available at https://doi.org/10.17487/RFC4892
Snippet:
IETF RFC 4892, Requirements for a Mechanism Identifying a Name Server Instance. Available at https://doi.org/10.17487/RFC4892

HTML (ISO 690 compliant)

Preview:
IETF RFC 4892, Requirements for a Mechanism Identifying a Name Server Instance. Available at https://doi.org/10.17487/RFC4892
Snippet:
<span class="citation"><cite>IETF RFC 4892</cite>, Requirements for a Mechanism Identifying a Name Server Instance. Available at <a href="https://doi.org/10.17487/RFC4892" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4892</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 4892, Requirements for a Mechanism Identifying a Name Server Instance
doi: 10.17487/RFC4892
url: https://doi.org/10.17487/RFC4892
Snippet:
<li>
<cite id="bib-rfc4892">IETF RFC 4892</cite>, Requirements for a Mechanism Identifying a Name Server Instance
<span class="doi">10.17487/RFC4892</span>
</li>

Referenced By