Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 15
- Abstract
- Formally, any DNS Resource Record (RR) may occur under any domain name. However, some services use an operational convention for defining specific interpretations of an RRset by locating the records in a DNS branch under the parent domain to which the RRset actually applies. The top of this subordinate branch is defined by a naming convention that uses a reserved node name, which begins with the underscore character (e.g., "_name"). The underscored naming construct defines a semantic scope for DNS record types that are associated with the parent domain above the underscored branch. This specification explores the nature of this DNS usage and defines the "Underscored and Globally Scoped DNS Node Names" registry with IANA. The purpose of this registry is to avoid collisions resulting from the use of the same underscored name for different services.
- Publication Date
- 2019-03-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC8552- Link
- https://doi.org/10.17487/RFC8552
- Author(s)
- Dave Crocker
- Keyword(s)
- DNS
Latest version of IETF RFC 8552
Document Versions — IETF RFC 8552
-
▶ IETF RFC 8552 (2019-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 952 [Active*]
- IETF RFC 1034 [Active*]
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 2119 [Active*]
- IETF RFC 2181 [Active*]
- IETF RFC 2782 [Active*]
- IETF RFC 3921 [Superseded*]
- IETF RFC 4386 [Active*]
- IETF RFC 5026 [Active*]
- IETF RFC 5509 [Active*]
- IETF RFC 5518 [Active*]
- IETF RFC 6118 [Active*]
- IETF RFC 6335 [Active*]
- IETF RFC 6376 [Active*]
- IETF RFC 6698 [Active*]
- IETF RFC 6763 [Active*]
- IETF RFC 7208 [Active*]
- IETF RFC 7489 [Superseded*]
- IETF RFC 7553 [Active*]
- IETF RFC 7566 [Active*]
- IETF RFC 7671 [Active*]
- IETF RFC 7929 [Active*]
- IETF RFC 8126 [Active*]
- IETF RFC 8145 [Active*]
- IETF RFC 8162 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8461 [Active*]
- IETF RFC 8555 [Active*]
Bibliographic Reference(s)
- IETF.draft-ietf-netconf-zerotouch-29 — ZEROTOUCH EXTERNAL
- IETF RFC 8553 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8552.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 8552, Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves. Available at https://doi.org/10.17487/RFC8552
Snippet:
IETF RFC 8552, Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves. Available at https://doi.org/10.17487/RFC8552
HTML (ISO 690 compliant)
Preview:
IETF RFC 8552, Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves. Available at https://doi.org/10.17487/RFC8552
Snippet:
<span class="citation"><cite>IETF RFC 8552</cite>, Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves. Available at <a href="https://doi.org/10.17487/RFC8552" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8552</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8552, Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves
doi: 10.17487/RFC8552
url: https://doi.org/10.17487/RFC8552
doi: 10.17487/RFC8552
url: https://doi.org/10.17487/RFC8552
Snippet:
<li> <cite id="bib-rfc8552">IETF RFC 8552</cite>, Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves <span class="doi">10.17487/RFC8552</span> </li>
Referenced By
- IETF RFC 8553 [Active*]
- IETF RFC 8572 [Active*]
- IETF RFC 9460 [Active*]
- IETF RFC 9461 [Active*]
- IETF RFC 9615 [Active*]
- IETF RFC 9989 [Active*]