AS112 Nameserver Operations
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 24
- Abstract
- Many sites connected to the Internet make use of IPv4 addresses that are not globally unique. Examples are the addresses designated in RFC 1918 for private use within individual sites. Devices in such environments may occasionally originate Domain Name System (DNS) queries (so-called "reverse lookups") corresponding to those private-use addresses. Since the addresses concerned have only local significance, it is good practice for site administrators to ensure that such queries are answered locally. However, it is not uncommon for such queries to follow the normal delegation path in the public DNS instead of being answered within the site. It is not possible for public DNS servers to give useful answers to such queries. In addition, due to the wide deployment of private-use addresses and the continuing growth of the Internet, the volume of such queries is large and growing. The AS112 project aims to provide a distributed sink for such queries in order to reduce the load on the corresponding authoritative servers. The AS112 project is named after the Autonomous System Number (ASN) that was assigned to it. This document describes the steps required to install a new AS112 node and offers advice relating to such a node's operation. This document obsoletes RFC 6304.
- Publication Date
- 2015-05-01
- Status Note
- Informational
- DOI
10.17487/RFC7534- Link
- https://doi.org/10.17487/RFC7534
- Author(s)
- Joe AbleyWilliam F. Maton
- Keyword(s)
- AS112, DNS, Reverse DNS, Anycast
Latest version of IETF RFC 7534
Document Versions — IETF RFC 7534
-
▶ IETF RFC 7534 (2015-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 1034 [Active*]
- IETF RFC 1918 [Active*]
- IETF RFC 2870 [Superseded*]
- IETF RFC 4033 [Active*]
- IETF RFC 4271 [Active*]
- IETF RFC 4786 [Active*]
- RFC7535 — RFC7535 EXTERNAL
Bibliographic Reference(s)
- IETF RFC 1876 [Active*]
- RFC5001 — RFC5001 EXTERNAL
- IETF RFC 5855 [Active*]
- IETF RFC 6303 [Active*]
- IETF RFC 6304 [Superseded*]
- IETF RFC 6305 [Active*]
- IETF RFC 6672 [Active*]
- IETF RFC 6890 [Active*]
- RFC7249 — RFC7249 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7534.json
Supersedes:
IETF RFC 6304 [Superseded*]
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 7534, AS112 Nameserver Operations. Available at https://doi.org/10.17487/RFC7534
Snippet:
IETF RFC 7534, AS112 Nameserver Operations. Available at https://doi.org/10.17487/RFC7534
HTML (ISO 690 compliant)
Preview:
IETF RFC 7534, AS112 Nameserver Operations. Available at https://doi.org/10.17487/RFC7534
Snippet:
<span class="citation"><cite>IETF RFC 7534</cite>, AS112 Nameserver Operations. Available at <a href="https://doi.org/10.17487/RFC7534" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7534</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7534, AS112 Nameserver Operations
doi: 10.17487/RFC7534
url: https://doi.org/10.17487/RFC7534
doi: 10.17487/RFC7534
url: https://doi.org/10.17487/RFC7534
Snippet:
<li> <cite id="bib-rfc7534">IETF RFC 7534</cite>, AS112 Nameserver Operations <span class="doi">10.17487/RFC7534</span> </li>
Referenced By
- IETF RFC 9210 [Active*]