Use of DNS Aliases for Network Services

Metadata

Publisher: IETF
Doc Type: Best Practice
Pages: 8
Abstract: It has become a common practice to use symbolic names (usually CNAMEs) in the Domain Name Service (DNS - [RFC-1034, RFC-1035]) to refer to network services such as anonymous FTP [RFC-959] servers, Gopher [RFC- 1436] servers, and most notably World-Wide Web HTTP [RFC-1945] servers. This is desirable for a number of reasons. It provides a way of moving services from one machine to another transparently, and a mechanism by which people or agents may programmatically discover that an organization runs, say, a World-Wide Web server. Although this approach has been almost universally adopted, there is no standards document or similar specification for these commonly used names. This document seeks to rectify this situation by gathering together the extant 'folklore' on naming conventions, and proposes a mechanism for accommodating new protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Publication Date: 1997-10-01
Status Note: Best Current Practice
DOI: 10.17487/RFC2219
Link: https://doi.org/10.17487/RFC2219
Author(s): Martin Hamilton
Russ Wright
Keyword(s): DNS

Latest version of IETF RFC 2219

Document Versions — IETF RFC 2219

▶ IETF RFC 2219 (1997-10-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

R. Hedberg, S. Dorner, P. Pomes. "The CCSO Nameserver (Ph) Architecture", Work in Progress. EXTERNAL
A. Emtage, P. Deutsch. "archie - An Electronic Directory Service for the Internet", Winter Usenix Conference Proceedings 1992. Pages 93-110. EXTERNAL
IETF RFC 768 [Active*]
IETF RFC 793 [Superseded*]
IETF RFC 821 [Superseded*]
IETF RFC 954 [Superseded*]
IETF RFC 959 [Active*]
IETF RFC 974 [Superseded*]
IETF RFC 977 [Superseded*]
IETF RFC 1034 [Active*]
IETF RFC 1035 [Active, Amended*]
IETF RFC 1123 [Active*]
IETF RFC 1288 [Active*]
IETF RFC 1305 [Superseded*]
IETF RFC 1436 [Active*]
IETF RFC 1590 [Superseded*]
IETF RFC 1625 [Active*]
IETF RFC 1700 [Superseded*]
IETF RFC 1714 [Superseded*]
IETF RFC 1777 [Superseded*]
IETF RFC 1912 [Active*]
IETF RFC 1939 [Active*]
IETF RFC 1945 [Active*]
IETF RFC 2052 [Superseded*]
IETF RFC 2065 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC2219.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 2219, Use of DNS Aliases for Network Services. Available at https://doi.org/10.17487/RFC2219

Snippet:

IETF RFC 2219, Use of DNS Aliases for Network Services. Available at https://doi.org/10.17487/RFC2219

HTML (ISO 690 compliant)

Preview:

IETF RFC 2219, Use of DNS Aliases for Network Services. Available at https://doi.org/10.17487/RFC2219

Snippet:

<span class="citation"><cite>IETF RFC 2219</cite>, Use of DNS Aliases for Network Services. Available at <a href="https://doi.org/10.17487/RFC2219" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2219</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 2219, Use of DNS Aliases for Network Services
doi: 10.17487/RFC2219
url: https://doi.org/10.17487/RFC2219

Snippet:

<li>
<cite id="bib-rfc2219">IETF RFC 2219</cite>, Use of DNS Aliases for Network Services
<span class="doi">10.17487/RFC2219</span>
</li>

Referenced By

IETF RFC 2782 [Active*]
IETF RFC 3118 [Active*]