Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Obsoleted by:

RFC 7534

Authors:

J. Abley
W. Maton

Stream:

IETF

Source:

dnsop (ops)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6304

Discuss this RFC: Send questions or comments to the mailing listdnsop@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6304

Abstract

Many sites connected to the Internet make use of IPv4 addresses thatare not globally unique. Examples are the addresses designated inRFC 1918 for private use within individual sites.

Devices in such environments may occasionally originate Domain NameSystem (DNS) queries (so-called "reverse lookups") corresponding tothose private-use addresses. Since the addresses concerned have onlylocal significance, it is good practice for site administrators toensure that such queries are answered locally. However, it is notuncommon for such queries to follow the normal delegation path in thepublic DNS instead of being answered within the site.

It is not possible for public DNS servers to give useful answers tosuch queries. In addition, due to the wide deployment of private-useaddresses and the continuing growth of the Internet, the volume ofsuch queries is large and growing. The AS112 project aims to providea distributed sink for such queries in order to reduce the load onthe IN-ADDR.ARPA authoritative servers. The AS112 project is namedafter the Autonomous System Number (ASN) that was assigned to it.

This document describes the steps required to install a new AS112node and offers advice relating to such a node's operation. This document is not an Internet Standards Track specification; it ispublished for informational purposes.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.