RFC 7534: AS112 Nameserver Operations
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7534
- Published
- May 2015
- Authors
- J. Abley; W. Sotomayor
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 24
- Also known as
- —
- Obsoletes:
- RFC 6304
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7535AS112 Redirection Using DNAMECurrent
May 2015
- RFC 7646Definition and Use of DNSSEC Negative Trust AnchorsCurrent
September 2015
- RFC 7344Automating DNSSEC Delegation Trust MaintenanceUpdated
September 2014
- RFC 7766DNS Transport over TCP - Implementation RequirementsUpdated
March 2016
- RFC 7828The edns-tcp-keepalive EDNS0 OptionCurrent
April 2016
- RFC 8027DNSSEC Roadblock AvoidanceCurrent
November 2016
- RFC 8145Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)Updated
April 2017
- RFC 6841A Framework for DNSSEC Policies and DNSSEC Practice StatementsCurrent
January 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?