Internet Engineering Task Force (IETF) J. Abley
Request for Comments: 6304 ICANN
Category: Informational W. Maton
ISSN: 2070-1721 NRC-CNRC
July 2011
Internet Engineering Task Force (IETF) J. Abley
Request for Comments: 6304 ICANN
Category: Informational W. Maton
ISSN: 2070-1721 NRC-CNRC
July 2011
AS112 Nameserver Operations
AS112名称服务器操作
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.
许多连接到Internet的站点使用的IPv4地址不是全局唯一的。例如，RFC 1918中指定的地址，供各个站点内的私人使用。
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.
此类环境中的设备有时可能会发起与这些专用地址对应的域名系统（DNS）查询（所谓的“反向查找”）。由于相关地址仅具有本地意义，因此站点管理员最好确保在本地回答此类查询。然而，这种查询遵循公共DNS中的正常委托路径而不是在站点内得到答复的情况并不少见。
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 IN-ADDR.ARPA authoritative servers. The AS112 project is named after the Autonomous System Number (ASN) that was assigned to it.
公共DNS服务器不可能为此类查询提供有用的答案。此外，由于私用地址的广泛部署和互联网的持续增长，此类查询的数量巨大且不断增长。AS112项目旨在为此类查询提供一个分布式接收器，以减少in-ADDR.ARPA权威服务器上的负载。AS112项目以分配给它的自治系统编号（ASN）命名。
This document describes the steps required to install a new AS112 node and offers advice relating to such a node's operation.
本文档描述了安装新AS112节点所需的步骤，并提供了有关此类节点操作的建议。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6304.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6304.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. AS112 DNS Service . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Zones . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Nameservers . . . . . . . . . . . . . . . . . . . . . . . 4
3. Installation of a New Node . . . . . . . . . . . . . . . . . . 5
3.1. Useful Background Knowledge . . . . . . . . . . . . . . . 5
3.2. Topological Location . . . . . . . . . . . . . . . . . . . 5
3.3. Operating System and Host Considerations . . . . . . . . . 5
3.4. Routing Software . . . . . . . . . . . . . . . . . . . . . 6
3.5. DNS Software . . . . . . . . . . . . . . . . . . . . . . . 8
3.6. Testing a Newly Installed Node . . . . . . . . . . . . . . 11
4. Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1. Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2. Downtime . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3. Statistics and Measurement . . . . . . . . . . . . . . . . 12
5. Communications . . . . . . . . . . . . . . . . . . . . . . . . 12
6. On the Future of AS112 Nodes . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. History . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. AS112 DNS Service . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Zones . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Nameservers . . . . . . . . . . . . . . . . . . . . . . . 4
3. Installation of a New Node . . . . . . . . . . . . . . . . . . 5
3.1. Useful Background Knowledge . . . . . . . . . . . . . . . 5
3.2. Topological Location . . . . . . . . . . . . . . . . . . . 5
3.3. Operating System and Host Considerations . . . . . . . . . 5
3.4. Routing Software . . . . . . . . . . . . . . . . . . . . . 6
3.5. DNS Software . . . . . . . . . . . . . . . . . . . . . . . 8
3.6. Testing a Newly Installed Node . . . . . . . . . . . . . . 11
4. Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1. Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2. Downtime . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3. Statistics and Measurement . . . . . . . . . . . . . . . . 12
5. Communications . . . . . . . . . . . . . . . . . . . . . . . . 12
6. On the Future of AS112 Nodes . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. History . . . . . . . . . . . . . . . . . . . . . . . 17
Many sites connected to the Internet make use of IPv4 addresses that are not globally unique. Examples are the addresses designated in [RFC1918] for private use within individual sites.
许多连接到Internet的站点使用的IPv4地址不是全局唯一的。例如，在[RFC1918]中指定的供各个站点内私人使用的地址。
Devices in such environments may occasionally originate Domain Name System (DNS) [RFC1034] 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 [RFC6303]. 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.
此类环境中的设备有时可能会发起与这些专用地址对应的域名系统（DNS）[RFC1034]查询（所谓的“反向查找”）。由于相关地址仅具有本地意义，因此站点管理员应确保在本地回答此类查询[RFC6303]。然而，这种查询遵循公共DNS中的正常委托路径而不是在站点内得到答复的情况并不少见。
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 IN-ADDR.ARPA authoritative servers [RFC5855].
公共DNS服务器不可能为此类查询提供有用的答案。此外，由于私用地址的广泛部署和互联网的持续增长，此类查询的数量巨大且不断增长。AS112项目旨在为此类查询提供分布式接收器，以减少in-ADDR.ARPA权威服务器上的负载[RFC5855]。
The AS112 project encompasses a loosely coordinated collection of independently operated nameservers. Each nameserver functions as a single node in an AS112 anycast cloud [RFC4786] and is configured to answer authoritatively for a particular set of nominated zones.
AS112项目包含一个松散协调的独立操作名称服务器集合。每个名称服务器作为AS112选播云[RFC4786]中的单个节点运行，并配置为对指定区域的特定集合进行授权应答。
The AS112 project is named after the Autonomous System Number (ASN) that was assigned to it.
AS112项目以分配给它的自治系统编号（ASN）命名。
AS112 nameservers answer authoritatively for the following zones, corresponding to [RFC1918] private-use netblocks:
AS112名称服务器对以下区域进行授权应答，对应于[RFC1918]专用NetBlock：
o 10.IN-ADDR.ARPA
o 10.IN-ADDR.ARPA
o 16.172.IN-ADDR.ARPA, 17.172.IN-ADDR.ARPA, ..., 31.172.IN-ADDR.ARPA
o 16.172.IN-ADDR.ARPA，17.172.IN-ADDR.ARPA，…，31.172.IN-ADDR.ARPA
o 168.192.IN-ADDR.ARPA
o 168.192.IN-ADDR.ARPA
and the following zone, corresponding to the "link local" netblock 169.254.0.0/16 listed in [RFC5735]:
以及以下区域，对应于[RFC5735]中列出的“链路本地”netblock 169.254.0.0/16：
o 254.169.IN-ADDR.ARPA
o 254.169.IN-ADDR.ARPA
To aid identification of AS112 anycast nodes, each node also answers authoritatively for the zone HOSTNAME.AS112.NET.
为了帮助识别AS112选播节点，每个节点还对区域HOSTNAME.AS112.NET进行授权应答。
See Section 3.5 for the recommended contents of all these zones.
所有这些区域的建议内容见第3.5节。
It is possible that other zones corresponding to private-use infrastructure will be delegated to AS112 servers in the future. A list of zones for which AS112 servers answer authoritatively is maintained at <http://www.as112.net/>.
将来可能会将与专用基础设施相对应的其他区域委托给AS112服务器。AS112服务器授权应答的区域列表保存在<http://www.as112.net/>.
The zones listed in Section 2.1 are delegated to the two nameservers BLACKHOLE-1.IANA.ORG (192.175.48.6) and BLACKHOLE-2.IANA.ORG (192.175.48.42).
第2.1节中列出的区域被委托给两个命名服务器BLACKHOLE-1.IANA.ORG（192.175.48.6）和BLACKHOLE-2.IANA.ORG（192.175.48.42）。
Additionally, the server PRISONER.IANA.ORG (192.175.48.1) is listed in the MNAME field of the SOA records of the IN-ADDR.ARPA zones served by AS112 nameservers. PRISONER.IANA.ORG receives mainly dynamic update queries.
此外，server.IANA.ORG（192.175.48.1）列在AS112名称服务器服务的in-ADDR.ARPA区域的SOA记录的MNAME字段中。ORG主要接收动态更新查询。
The addresses of all these nameservers are covered by the single IPv4 prefix 192.175.48.0/24.
所有这些名称服务器的地址都由单个IPv4前缀192.175.48.0/24覆盖。
Installation of an AS112 node is relatively straightforward. However, experience in the following general areas may prove useful:
AS112节点的安装相对简单。但是，以下一般领域的经验可能会证明是有用的：
o inter-domain routing with BGP [RFC4271];
o BGP域间路由[RFC4271]；
o DNS authoritative server operations; and
o DNS权威服务器操作；和
o anycast [RFC4786] distribution of DNS services.
o anycast[RFC4786]DNS服务的分发。
AS112 nodes may be located anywhere on the Internet. For nodes that are intended to provide a public service to the Internet community (as opposed to private use), it may well be advantageous to choose a location that is easily (and cheaply) reachable by multiple providers, such as an Internet Exchange Point.
AS112节点可以位于Internet上的任何位置。对于打算向互联网社区提供公共服务（而非私人使用）的节点，选择多个提供商容易（且便宜）到达的位置（例如互联网交换点）很可能是有利的。
AS112 nodes may advertise their service prefix to BGP peers for local use (analogous to a conventional peering relationship between two providers) or for global use (analogous to a customer relationship with one or more providers).
AS112节点可向BGP对等方公布其服务前缀以供本地使用（类似于两个提供商之间的传统对等关系）或供全局使用（类似于与一个或多个提供商的客户关系）。
It is good operational practice to notify the community of users that may fall within the reach of a new AS112 node before it is installed. At an Internet Exchange, local mailing lists usually exist to facilitate such announcements. For nodes that are intended to be globally reachable, coordination with other AS112 operators is highly recommended. See also Section 5.
在安装新AS112节点之前，向社区通知可能在其范围内的用户是一种良好的操作实践。在互联网交换中，通常存在本地邮件列表以方便此类公告。对于计划全局可访问的节点，强烈建议与其他AS112运营商协调。另见第5节。
Examples in this document are based on UNIX and UNIX-like operating systems, but other operating systems exist that are suitable for use in construction of an AS112 node.
本文档中的示例基于UNIX和类UNIX操作系统，但也存在适合用于构建AS112节点的其他操作系统。
The chosen platform should include either support for cloned loopback interfaces or the capability to bind multiple addresses to a single loopback interface. The addresses of the nameservers listed in Section 2.2 will be configured on these interfaces in order that the DNS software can respond to queries properly.
所选平台应包括对克隆环回接口的支持或将多个地址绑定到单个环回接口的能力。第2.2节中列出的名称服务器地址将在这些接口上配置，以便DNS软件能够正确响应查询。
A host that is configured to act as an AS112 anycast node should be dedicated to that purpose and should not be used to simultaneously provide other services. This guidance is provided due to the unpredictable (and occasionally high) traffic levels that AS112 nodes have been seen to attract.
配置为充当AS112选播节点的主机应专用于此目的，且不应用于同时提供其他服务。由于AS112节点所吸引的流量水平不可预测（有时甚至很高），因此提供了此指导。
System startup scripts should be arranged such that the various AS112-related components start automatically following a system reboot. The order in which interfaces are configured and software components started should be arranged such that routing software startup follows DNS software startup, and DNS software startup follows loopback interface configuration.
系统启动脚本的安排应确保各种AS112相关组件在系统重新启动后自动启动。接口配置和软件组件启动的顺序应安排为：路由软件启动遵循DNS软件启动，DNS软件启动遵循环回接口配置。
Wrapper scripts or other arrangements should be employed to ensure that the anycast service prefix for AS112 is not advertised while either the anycast addresses are not configured or the DNS software is not running.
应采用包装器脚本或其他安排，以确保在未配置选播地址或DNS软件未运行时，AS112的选播服务前缀不会被通告。
AS112 nodes signal the availability of AS112 nameservers to the Internet using BGP [RFC4271]: each AS112 node is a BGP speaker and announces the prefix 192.175.48.0/24 to the Internet with origin AS 112 (see also Section 2.2).
AS112节点使用BGP向Internet发送AS112名称服务器可用性信号[RFC4271]：每个AS112节点都是BGP演讲者，并向Internet宣布前缀192.175.48.0/24，来源为112（另请参见第2.2节）。
The examples in this document are based on the Quagga Routing Suite [QUAGGA] running on Linux, but other software packages exist that also provide suitable BGP support for AS112 nodes.
本文档中的示例基于Linux上运行的Quagga路由套件[Quagga]，但也有其他软件包为AS112节点提供适当的BGP支持。
The "bgpd.conf" file is used by Quagga's bgpd daemon, which provides BGP support. The router ID in this example is 203.0.113.1; the AS112 node peers with external peers 192.0.2.1 and 192.0.2.2. Note the local AS number is 112, and the service prefix originated from the AS112 node is 192.175.48.0/24.
Quagga的bgpd守护程序使用“bgpd.conf”文件，该守护程序提供BGP支持。本例中的路由器ID为203.0.113.1；AS112节点与外部节点192.0.2.1和192.0.2.2对等。注意，本地AS编号为112，来自AS112节点的服务前缀为192.175.48.0/24。
! bgpd.conf ! hostname as112-bgpd password <something> enable password <supersomething> ! ! Note that all AS112 nodes use the local Autonomous System ! Number 112, and originate the IPv4 prefix 192.175.48.0/24. ! All other addresses shown below are illustrative, and ! actual numbers will depend on local circumstances. ! router bgp 112 bgp router-id 203.0.113.1 network 192.175.48.0 neighbor 192.0.2.1 remote-as 64496 neighbor 192.0.2.1 next-hop-self neighbor 192.0.2.1 prefix-list AS112 out neighbor 192.0.2.1 filter-list 1 out neighbor 192.0.2.2 remote-as 64497 neighbor 192.0.2.2 next-hop-self neighbor 192.0.2.2 prefix-list AS112 out neighbor 192.0.2.2 filter-list 1 out ! ip prefix-list AS112 permit 192.175.48.0/24 ! ip as-path access-list 1 permit ^$
! bgpd.conf！主机名as112 bgpd密码<something>启用密码<supersomething>！请注意，所有AS112节点都使用本地自治系统！编号112，并起始IPv4前缀192.175.48.0/24！下面显示的所有其他地址都是说明性的，并且！实际人数将取决于当地情况！路由器bgp 112 bgp路由器id 203.0.113.1网络192.175.48.0邻居192.0.2.1远程as 64496邻居192.0.2.1下一跳自邻居192.0.2.1前缀列表AS112出邻居192.0.2.1筛选器列表1出邻居192.0.2.2远程as 64497邻居192.0.2下一跳自邻居192.0.2.2前缀列表AS112出邻居192.0.2筛选器列表1出来ip前缀列表AS112允许192.175.48.0/24！ip作为路径访问列表1允许^$
The configuration above includes a double-blinded restriction on what the AS112 node shall advertise to the pair of BGP neighbors. Firstly, that prefix-list "AS112" only containing the service prefix 192.175.48.0/24 shall be advertised. Secondly, the "ip as-path access-list 1" statement contains a one-line regular expression that permits only the local AS number (112 in this case) and no other to be advertised as well. Both statements prevent the node from becoming a transit router. Equivalent restrictions using other BGP implementations should be utilised.
上述配置包括对AS112节点应向一对BGP邻居播发的内容的双盲限制。首先，应公布仅包含服务前缀192.175.48.0/24的前缀列表“AS112”。其次，“ip as path access list 1”语句包含一行正则表达式，该正则表达式只允许本地as编号（在本例中为112），也不允许播发其他as编号。这两条语句都阻止节点成为传输路由器。应使用其他BGP实施的同等限制。
The "zebra.conf" file is required to provide integration between protocol daemons (bgpd, in this case) and the kernel.
需要“zebra.conf”文件来提供协议守护进程（本例中为bgpd）和内核之间的集成。
! zebra.conf ! hostname as112 password <something> enable password <supersomething> ! interface lo ! interface eth0 !
! 斑马军团！主机名as112密码<something>启用密码<supersomething>！接口lo！接口eth0！
Although the queries received by AS112 nodes are definitively misdirected, it is important that they be answered in a manner that is accurate and consistent. For this reason, AS112 nodes operate as fully functional and standards-compliant DNS authoritative servers [RFC1034], and hence require DNS software.
尽管AS112节点接收到的查询肯定是错误的，但以准确一致的方式回答它们是很重要的。因此，AS112节点作为功能齐全且符合标准的DNS权威服务器[RFC1034]运行，因此需要DNS软件。
Examples in this document are based on ISC BIND9 [BIND], but other DNS software exists that is suitable for use in construction of an AS112 node.
本文档中的示例基于ISC BIND9[BIND]，但存在适合用于构建AS112节点的其他DNS软件。
The following is a sample BIND9 "named.conf" file for a dedicated AS112 server. Note that the nameserver is configured to act as an authoritative-only server (i.e., recursion is disabled). The nameserver is also configured to listen on the various AS112 anycast nameserver addresses, as well as its local addresses.
以下是专用AS112服务器的示例BIND9“named.conf”文件。请注意，名称服务器被配置为仅作为权威服务器（即，禁用递归）。名称服务器还配置为侦听各种AS112选播名称服务器地址及其本地地址。
// named.conf
//named.conf
// global options
//全球选择
options {
listen-on {
127.0.0.1; // localhost
options {
listen-on {
127.0.0.1; // localhost
// The following address is node-dependent and should be set to // something appropriate for the new AS112 node.
//以下地址依赖于节点，应设置为//适合新AS112节点的某个地址。
203.0.113.1; // local address (globally unique, unicast)
203.0.113.1; // local address (globally unique, unicast)
// the following addresses correspond to AS112 addresses, and
// are the same for all AS112 nodes
// the following addresses correspond to AS112 addresses, and
// are the same for all AS112 nodes
192.175.48.1; // prisoner.iana.org (anycast)
192.175.48.6; // blackhole-1.iana.org (anycast)
192.175.48.42; // blackhole-2.iana.org (anycast)
192.175.48.1; // prisoner.iana.org (anycast)
192.175.48.6; // blackhole-1.iana.org (anycast)
192.175.48.42; // blackhole-2.iana.org (anycast)
};
directory "/var/named";
recursion no; // authoritative-only server
query-source address *;
};
};
directory "/var/named";
recursion no; // authoritative-only server
query-source address *;
};
// Log queries, so that when people call us about unexpected
// answers to queries they didn't realise they had sent, we
// have something to talk about. Note that activating this
// has the potential to create high CPU load and consume
// enormous amounts of disk space.
// Log queries, so that when people call us about unexpected
// answers to queries they didn't realise they had sent, we
// have something to talk about. Note that activating this
// has the potential to create high CPU load and consume
// enormous amounts of disk space.
logging {
channel "querylog" {
file "/var/log/query.log" versions 2 size 500m;
print-time yes;
};
category queries { querylog; };
};
logging {
channel "querylog" {
file "/var/log/query.log" versions 2 size 500m;
print-time yes;
};
category queries { querylog; };
};
// RFC 1918
//RFC1918
zone "10.in-addr.arpa" { type master; file "db.empty"; };
zone "16.172.in-addr.arpa" { type master; file "db.empty"; };
zone "17.172.in-addr.arpa" { type master; file "db.empty"; };
zone "18.172.in-addr.arpa" { type master; file "db.empty"; };
zone "19.172.in-addr.arpa" { type master; file "db.empty"; };
zone "20.172.in-addr.arpa" { type master; file "db.empty"; };
zone "21.172.in-addr.arpa" { type master; file "db.empty"; };
zone "22.172.in-addr.arpa" { type master; file "db.empty"; };
zone "23.172.in-addr.arpa" { type master; file "db.empty"; };
zone "24.172.in-addr.arpa" { type master; file "db.empty"; };
zone "25.172.in-addr.arpa" { type master; file "db.empty"; };
zone "26.172.in-addr.arpa" { type master; file "db.empty"; };
zone "27.172.in-addr.arpa" { type master; file "db.empty"; };
zone "28.172.in-addr.arpa" { type master; file "db.empty"; };
zone "29.172.in-addr.arpa" { type master; file "db.empty"; };
zone "30.172.in-addr.arpa" { type master; file "db.empty"; };
zone "31.172.in-addr.arpa" { type master; file "db.empty"; };
zone "168.192.in-addr.arpa" { type master; file "db.empty"; };
zone "10.in-addr.arpa" { type master; file "db.empty"; };
zone "16.172.in-addr.arpa" { type master; file "db.empty"; };
zone "17.172.in-addr.arpa" { type master; file "db.empty"; };
zone "18.172.in-addr.arpa" { type master; file "db.empty"; };
zone "19.172.in-addr.arpa" { type master; file "db.empty"; };
zone "20.172.in-addr.arpa" { type master; file "db.empty"; };
zone "21.172.in-addr.arpa" { type master; file "db.empty"; };
zone "22.172.in-addr.arpa" { type master; file "db.empty"; };
zone "23.172.in-addr.arpa" { type master; file "db.empty"; };
zone "24.172.in-addr.arpa" { type master; file "db.empty"; };
zone "25.172.in-addr.arpa" { type master; file "db.empty"; };
zone "26.172.in-addr.arpa" { type master; file "db.empty"; };
zone "27.172.in-addr.arpa" { type master; file "db.empty"; };
zone "28.172.in-addr.arpa" { type master; file "db.empty"; };
zone "29.172.in-addr.arpa" { type master; file "db.empty"; };
zone "30.172.in-addr.arpa" { type master; file "db.empty"; };
zone "31.172.in-addr.arpa" { type master; file "db.empty"; };
zone "168.192.in-addr.arpa" { type master; file "db.empty"; };
// RFC 5735
//RFC 5735
zone "254.169.in-addr.arpa" { type master; file "db.empty"; };
zone "254.169.in-addr.arpa" { type master; file "db.empty"; };
// Also answer authoritatively for the HOSTNAME.AS112.NET zone, // which contains data of operational relevance.
//还可以权威性地回答HOSTNAME.AS112.NET区域，该区域包含与操作相关的数据。
zone "hostname.as112.net" {
type master;
file "db.hostname.as112.net";
};
zone "hostname.as112.net" {
type master;
file "db.hostname.as112.net";
};
The "db.empty" file follows, below. This is the source data used to populate all the IN-ADDR.ARPA zones listed in Section 2.1. Note that the RNAME specified in the SOA record corresponds to hostmaster@root-servers.org, a suitable email address for receiving technical queries about these zones.
下面是“db.empty”文件。这是用于填充第2.1节中列出的所有IN-ADDR.ARPA区域的源数据。请注意，SOA记录中指定的RNAME对应于hostmaster@root-servers.org，用于接收有关这些区域的技术查询的合适电子邮件地址。
; db.empty
;
; Empty zone for AS112 server.
;
$TTL 1W
@ IN SOA prisoner.iana.org. hostmaster.root-servers.org. (
1 ; serial number
1W ; refresh
1M ; retry
1W ; expire
1W ) ; negative caching TTL
;
NS blackhole-1.iana.org.
NS blackhole-2.iana.org.
;
; There should be no other resource records included in this zone.
;
; Records that relate to RFC 1918-numbered resources within the
; site hosting this AS112 node should not be hosted on this
; nameserver.
; db.empty
;
; Empty zone for AS112 server.
;
$TTL 1W
@ IN SOA prisoner.iana.org. hostmaster.root-servers.org. (
1 ; serial number
1W ; refresh
1M ; retry
1W ; expire
1W ) ; negative caching TTL
;
NS blackhole-1.iana.org.
NS blackhole-2.iana.org.
;
; There should be no other resource records included in this zone.
;
; Records that relate to RFC 1918-numbered resources within the
; site hosting this AS112 node should not be hosted on this
; nameserver.
The "db.hostname.as112.net" file follows, below. This zone contains various resource records that provide operational data to users for troubleshooting or measurement purposes; the data should be edited to suit local circumstances. Note that the response to the query "HOSTNAME.AS112.NET IN TXT" should fit within a 512-octet DNS/UDP datagram: i.e., it should be available over UDP transport without requiring EDNS0 support.
下面是“db.hostname.as112.net”文件。该区域包含各种资源记录，这些记录为用户提供操作数据，用于故障排除或测量目的；应根据当地情况对数据进行编辑。请注意，对查询“HOSTNAME.AS112.NET IN TXT”的响应应包含在512个八位字节的DNS/UDP数据报中：即，它应可通过UDP传输而无需EDNS0支持。
The optional LOC record [RFC1876] included in the zone apex provides information about the geospatial location of the node.
分区顶点中包含的可选LOC记录[RFC1876]提供了有关节点地理空间位置的信息。
; db.hostname.as112.net
;
$TTL 1W
@ SOA server.example.net. admin.example.net. (
1 ; serial number
1W ; refresh
1M ; retry
1W ; expire
1W ) ; negative caching TTL
;
NS blackhole-2.iana.org.
NS blackhole-1.iana.org.
;
TXT "Name of Facility or similar" "City, Country"
TXT "See http://www.as112.net/ for more information."
;
LOC 45 25 0.000 N 75 42 0.000 W 80.00m 1m 10000m 10m
; db.hostname.as112.net
;
$TTL 1W
@ SOA server.example.net. admin.example.net. (
1 ; serial number
1W ; refresh
1M ; retry
1W ; expire
1W ) ; negative caching TTL
;
NS blackhole-2.iana.org.
NS blackhole-1.iana.org.
;
TXT "Name of Facility or similar" "City, Country"
TXT "See http://www.as112.net/ for more information."
;
LOC 45 25 0.000 N 75 42 0.000 W 80.00m 1m 10000m 10m
The BIND9 tool "dig" can be used to retrieve the TXT resource records associated with the domain "HOSTNAME.AS112.NET", directed at one of the AS112 anycast nameserver addresses. Continuing the example from above, the response received should indicate the identity of the AS112 node that responded to the query. See Section 3.5 for more details about the resource records associated with "HOSTNAME.AS112.NET".
BIND9工具“dig”可用于检索与域“HOSTNAME.AS112.NET”关联的TXT资源记录，该域指向AS112任意广播名称服务器地址之一。继续上面的示例，收到的响应应该指示响应查询的AS112节点的标识。有关与“HOSTNAME.AS112.NET”关联的资源记录的更多详细信息，请参见第3.5节。
% dig @prisoner.iana.org hostname.as112.net txt +short +norec
"Name of Facility or similar" "City, Country"
"See http://www.as112.net/ for more information."
%
% dig @prisoner.iana.org hostname.as112.net txt +short +norec
"Name of Facility or similar" "City, Country"
"See http://www.as112.net/ for more information."
%
If the response received indicates a different node is being used, then there is probably a routing problem to solve. If there is no response received at all, there might be a host or nameserver problem. Judicious use of tools such as traceroute and consultation of BGP looking glasses might be useful in troubleshooting.
如果收到的响应表明正在使用不同的节点，则可能需要解决路由问题。如果根本没有收到响应，则可能存在主机或名称服务器问题。明智地使用traceroute和BGP眼镜咨询等工具可能有助于故障排除。
Note that an appropriate set of tests for a new server will include queries sent from many different places within the expected service area of the node, using both UDP and TCP transport, and exercising all three AS112 anycast nameserver addresses.
请注意，新服务器的一组适当测试将包括从节点预期服务区域内的许多不同位置发送的查询，使用UDP和TCP传输，并执行所有三个AS112选播名称服务器地址。
AS112 nodes should be monitored to ensure they are functioning correctly, just as with any other production service. An AS112 node that stops answering queries correctly can cause failures and timeouts in unexpected places and can lead to failures in dependent systems that can be difficult to troubleshoot.
应监控AS112节点，以确保它们与任何其他生产服务一样正常运行。停止正确回答查询的AS112节点可能会在意外的地方导致故障和超时，并可能导致从属系统中难以排除的故障。
An AS112 node that needs to go off-line (e.g., for planned maintenance or as part of the diagnosis of some problem) should stop advertising the AS112 service prefix to its BGP peers. This can be done by shutting down the routing software on the node altogether or by causing the routing system to withdraw the route.
需要离线的AS112节点（例如，用于计划维护或作为某些问题诊断的一部分）应停止向其BGP对等方公布AS112服务前缀。这可以通过完全关闭节点上的路由软件或使路由系统退出路由来实现。
Withdrawing the service prefix is important in order to avoid blackholing query traffic in the event that the DNS software on the node is not functioning normally.
在节点上的DNS软件无法正常运行的情况下，撤销服务前缀对于避免黑洞查询流量非常重要。
Use of the AS112 node should be measured in order to track long-term trends, identify anomalous conditions, and ensure that the configuration of the AS112 node is sufficient to handle the query load.
应测量AS112节点的使用情况，以便跟踪长期趋势，识别异常情况，并确保AS112节点的配置足以处理查询负载。
Examples of free monitoring tools that might be useful to operators of AS112 nodes include:
AS112节点的操作员可能有用的免费监视工具示例包括：
o bindgraph [BINDGRAPH]
o bindgraph[bindgraph]
o dnstop [DNSTOP]
o dnstop[dnstop]
o DSC [DSC]
o DSC[DSC]
It is good operational practice to notify the community of users that may fall within the reach of a new AS112 node before it is installed. At Internet Exchanges, local mailing lists usually exist to facilitate such announcements.
在安装新AS112节点之前，向社区通知可能在其范围内的用户是一种良好的操作实践。在互联网交易所，通常存在本地邮件列表，以方便此类公告。
For nodes that are intended to be globally reachable, coordination with other AS112 operators is especially recommended. The mailing list <as112-ops@lists.dns-oarc.net> is operated for this purpose.
对于打算全局可访问的节点，特别建议与其他AS112运营商协调。邮件列表<as112-ops@lists.dns-oarc.net>就是为此而运行的。
Information pertinent to AS112 operations is maintained at <http://www.as112.net/>.
与AS112操作相关的信息保存在<http://www.as112.net/>.
Information about an AS112 node should also be published within the DNS, within the "HOSTNAME.AS112.NET" zone. See Section 3.5 for more details.
关于AS112节点的信息也应该在DNS中的“HOSTNAME.AS112.NET”区域中发布。详见第3.5节。
It is recommended practice for the operators of recursive nameservers to answer queries for zones served by AS112 nodes locally, such that queries never have an opportunity to reach AS112 servers [RFC6303]. Operational experience with AS112 nodes does not currently indicate an observable trend towards compliance with those recommendations, however.
建议递归名称服务器的操作员在本地回答AS112节点所服务区域的查询，这样查询就永远不会有机会到达AS112服务器[RFC6303]。然而，AS112节点的运行经验目前并未表明遵守这些建议的明显趋势。
It is expected that some DNS software vendors will include default configuration that will implement measures such as those described in [RFC6303]. If such software is widely deployed, it is reasonable to assume that the query load received by AS112 nodes will decrease; however, it is safe to assume that the query load will not decrease to zero, and consequently that AS112 nodes will continue to provide a useful service for the foreseeable future.
预计一些DNS软件供应商将包括默认配置，以实现[RFC6303]中所述的措施。如果这种软件被广泛部署，可以合理地假设AS112节点接收到的查询负载将减少；然而，可以安全地假设查询负载不会减少到零，因此AS112节点将在可预见的未来继续提供有用的服务。
There may be a requirement in the future for AS112 nodes to answer for their current set of zones over IPv6 transport. Such a requirement would necessitate the assignment of a corresponding IPv6 netblock for use as an anycast service prefix.
将来可能需要AS112节点通过IPv6传输为其当前区域集负责。这样的要求将需要分配相应的IPv6 netblock以用作选播服务前缀。
There may be a requirement in the future for AS112 nodes to serve additional zones or to stop serving particular zones that are currently served. Such changes would be widely announced in operational forums and published at <http://www.as112.net/>.
将来可能需要AS112节点为其他区域提供服务或停止为当前服务的特定区域提供服务。这些变化将在运营论坛上广泛公布，并在<http://www.as112.net/>.
The AS112 nameservers are all named under the domain IANA.ORG (see Section 2.2). However, the anycast infrastructure itself is operated by a loosely coordinated, diverse mix of organisations across the Internet, and is not an IANA function.
AS112命名服务器均在域名IANA.ORG下命名（见第2.2节）。然而，选播基础设施本身是由互联网上松散协调、多样化的组织组合运营的，不是IANA的职能。
The Autonomous System Number 112 and the IPv4 prefix 192.175.48.0/24 were assigned by ARIN.
自主系统编号112和IPv4前缀192.175.48.0/24由ARIN分配。
Hosts should never normally send queries to AS112 servers; queries relating to private-use addresses should be answered locally within a site. Hosts that send queries to AS112 servers may well leak information relating to private infrastructure to the public network, and this could present a security risk. This risk is orthogonal to the presence or absence of authoritative servers for these zones in the public DNS infrastructure, however.
主机通常不应向AS112服务器发送查询；与私人使用地址相关的查询应在现场本地回答。向AS112服务器发送查询的主机很可能会将与私有基础设施相关的信息泄漏到公共网络，这可能会带来安全风险。然而，这种风险与公共DNS基础设施中这些区域是否存在权威服务器是正交的。
Queries that are answered by AS112 servers are usually unintentional; it follows that the responses from AS112 servers are usually unexpected. Unexpected inbound traffic can trigger intrusion detection systems or alerts by firewalls. Operators of AS112 servers should be prepared to be contacted by operators of remote infrastructure who believe their security has been violated. Advice to those who mistakenly believe that responses from AS112 nodes constitute an attack on their infrastructure can be found in [RFC6305].
AS112服务器回答的查询通常是无意的；因此，来自AS112服务器的响应通常是意外的。意外的入站流量可能触发入侵检测系统或防火墙警报。AS112服务器的运营商应准备好让远程基础设施的运营商联系，他们认为他们的安全性受到了侵犯。对于那些错误地认为AS112节点的响应构成对其基础设施的攻击的人，可以在[RFC6305]中找到建议。
The deployment of AS112 nodes is very loosely coordinated compared to other services distributed using anycast. The malicious compromise of an AS112 node and subversion of the data served by the node are hence more difficult to detect due to the lack of central management. Since it is conceivable that changing the responses to queries received by AS112 nodes might influence the behaviour of the hosts sending the queries, such a compromise might be used as an attack vector against private infrastructure.
与使用选播分发的其他服务相比，AS112节点的部署非常松散。因此，由于缺乏集中管理，AS112节点的恶意危害和节点所服务数据的破坏更难检测。由于可以想象的是，改变AS112节点接收到的查询的响应可能会影响发送查询的主机的行为，这样的折衷可以用作攻击私有基础设施的攻击向量。
Operators of AS112 should take appropriate measures to ensure that AS112 nodes are appropriately protected from compromise, such as would normally be employed for production nameserver or network infrastructure. The guidance provided for root nameservers in [RFC2870] may be instructive.
AS112的运营商应采取适当的措施，以确保AS112节点得到适当的保护，免受危害，例如通常用于生产名称服务器或网络基础设施的节点。[RFC2870]中为根名称服务器提供的指导可能具有指导意义。
The zones hosted by AS112 servers are not signed with DNSSEC [RFC4033]. Given the distributed and loosely coordinated structure of the AS112 service, the zones concerned could only be signed if the private key material used was effectively public, obviating any security benefit resulting from the use of those keys.
AS112服务器承载的区域未使用DNSSEC[RFC4033]签名。考虑到AS112服务的分布式和松散协调结构，只有在使用的私钥材料有效公开的情况下，才能签署相关区域，从而避免使用这些密钥带来的任何安全好处。
The authors wish to acknowledge the assistance of Bill Manning, John Brown, Marco D'Itri, Daniele Arena, Stephane Bortzmeyer, Frank Habicht, Chris Thompson, Peter Losher, Peter Koch, Alfred Hoenes, S. Moonesamy, and Mehmet Akcin in the preparation of this document.
作者希望感谢Bill Manning、John Brown、Marco D'Itri、Daniele Arena、Stephane Bortzmeyer、Frank Habicht、Chris Thompson、Peter Losher、Peter Koch、Alfred Hoenes、S.Moonesamy和Mehmet Akcin在编写本文件过程中提供的协助。
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, November 1987.
[RFC1034]Mockapetris，P.，“域名-概念和设施”，STD 13，RFC 1034，1987年11月。
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and E. Lear, "Address Allocation for Private Internets", BCP 5, RFC 1918, February 1996.
[RFC1918]Rekhter，Y.，Moskowitz，R.，Karrenberg，D.，Groot，G.，和E.Lear，“私人互联网地址分配”，BCP 5，RFC 1918，1996年2月。
[RFC2870] Bush, R., Karrenberg, D., Kosters, M., and R. Plzak, "Root Name Server Operational Requirements", BCP 40, RFC 2870, June 2000.
[RFC2870]Bush，R.，Karrenberg，D.，Kosters，M.，和R.Plzak，“根名称服务器操作要求”，BCP 40，RFC 28702000年6月。
[RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, "DNS Security Introduction and Requirements", RFC 4033, March 2005.
[RFC4033]Arends，R.，Austein，R.，Larson，M.，Massey，D.，和S.Rose，“DNS安全介绍和要求”，RFC 4033，2005年3月。
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4271]Rekhter，Y.，Li，T.，和S.Hares，“边境网关协议4（BGP-4）”，RFC 42712006年1月。
[RFC4786] Abley, J. and K. Lindqvist, "Operation of Anycast Services", BCP 126, RFC 4786, December 2006.
[RFC4786]Abley，J.和K.Lindqvist，“任意广播服务的运营”，BCP 126，RFC 4786，2006年12月。
[BIND] Internet Systems Consortium, "BIND", <http://www.isc.org/software/BIND/>.
[BIND]互联网系统联盟，“BIND”<http://www.isc.org/software/BIND/>.
[BINDGRAPH] Delaurenti, M. and M. d'Itri, "bindgraph", <http://www.linux.it/~md/software/>.
[BINDGRAPH]Delaurenti，M.和M.d'Itri，“BINDGRAPH”<http://www.linux.it/~md/software/>。
[DNSTOP] The Measurement Factory, "Dnstop: Stay on Top of Your DNS Traffic", <http://dns.measurement-factory.com/tools/dnstop/>.
[DNSTOP]测量工厂，“DNSTOP:保持DNS流量的顶部”<http://dns.measurement-factory.com/tools/dnstop/>.
[DSC] The Measurement Factory, "Dsc: A DNS Statistics Collector", <http://dns.measurement-factory.com/tools/dsc/>.
[DSC]测量工厂，“DSC:DNS统计数据收集器”<http://dns.measurement-factory.com/tools/dsc/>.
[QUAGGA] "Quagga Software Routing Suite", <http://www.quagga.net>.
[QUAGGA]“QUAGGA软件路由套件”<http://www.quagga.net>.
[RFC1876] Davis, C., Vixie, P., Goodwin, T., and I. Dickinson, "A Means for Expressing Location Information in the Domain Name System", RFC 1876, January 1996.
[RFC1876]Davis，C.，Vixie，P.，Goodwin，T.，和I.Dickinson，“域名系统中表达位置信息的方法”，RFC1876，1996年1月。
[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", BCP 153, RFC 5735, January 2010.
[RFC5735]Cotton，M.和L.Vegoda，“特殊用途IPv4地址”，BCP 153，RFC 57352010年1月。
[RFC5855] Abley, J. and T. Manderson, "Nameservers for IPv4 and IPv6 Reverse Zones", BCP 155, RFC 5855, May 2010.
[RFC5855]Abley，J.和T.Manderson，“IPv4和IPv6反向区域的名称服务器”，BCP 155，RFC 5855，2010年5月。
[RFC6303] Andrews, M., "Locally Served DNS Zones", BCP 163, RFC 6303, July 2011.
[RFC6303]Andrews，M.，“本地服务DNS区域”，BCP 163，RFC 6303，2011年7月。
[RFC6305] Abley, J. and W. Maton, "I'm Being Attacked by PRISONER.IANA.ORG!", RFC 6305, July 2011.
[RFC6305]Abley，J.和W.Maton，“我被囚犯攻击了。IANA.ORG！”，RFC63052011年7月。
Widespread use of the private address blocks listed in [RFC1918] followed that document's publication in 1996. At that time the IN-ADDR.ARPA zone was served by root servers.
[RFC1918]中列出的私有地址块在1996年该文件发布后被广泛使用。当时，IN-ADDR.ARPA区域由根服务器提供服务。
The idea of off-loading IN-ADDR.ARPA queries relating to [RFC1918] addresses from the root nameservers was first proposed by Bill Manning and John Brown.
Bill Manning和John Brown首先提出了从根名称服务器卸载与[RFC1918]地址相关的IN-ADDR.ARPA查询的想法。
The use of anycast for distributing authoritative DNS service for [RFC1918] IN-ADDR.ARPA zones was subsequently proposed at a private meeting of root server operators.
随后，在根服务器运营商的一次私人会议上，提议使用anycast为[RFC1918]IN-ADDR.ARPA区域分发权威DNS服务。
ARIN provided an IPv4 prefix for the anycast service and also the autonomous system number 112 for use in originating that prefix. This assignment gave the project its name.
ARIN为选播服务提供了IPv4前缀，还提供了自治系统编号112，用于发起该前缀。这项任务为该项目命名。
In 2002, the first AS112 anycast nodes were deployed.
2002年，部署了第一批AS112选播节点。
In 2011, the IN-ADDR.ARPA zone was redelegated from the root servers to a new set of servers operated independently by AfriNIC, APNIC, ARIN, ICANN, LACNIC, and the RIPE NCC and named according to [RFC5855].
2011年，In-ADDR.ARPA区域从根服务器重新分配到由AfriNIC、APNIC、ARIN、ICANN、LACNIC和成熟的NCC独立运行的一组新服务器，并根据[RFC5855]命名。
The use of anycast nameservers in the AS112 project contributed to the operational experience of anycast DNS services, and it can be seen as a precursor to the anycast distribution of other authoritative DNS servers in subsequent years (e.g., various root servers).
在AS112项目中使用anycast名称服务器有助于提高anycast DNS服务的运营经验，并且可以将其视为其他权威DNS服务器（例如，各种根服务器）在随后几年中的anycast分发的先驱。
Authors' Addresses
作者地址
Joe Abley ICANN 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292 US
Joe Abley ICANN 4676金钟路330号套房马里纳德雷，美国加利福尼亚州90292
Phone: +1 519 670 9327
EMail: joe.abley@icann.org
Phone: +1 519 670 9327
EMail: joe.abley@icann.org
William F. Maton Sotomayor National Research Council of Canada 1200 Montreal Road Ottawa, ON K1A 0R6 Canada
William F.Maton Sotomayor加拿大国家研究委员会，位于加拿大K1A 0R6的渥太华蒙特利尔路1200号
Phone: +1 613 993 0880
EMail: wmaton@ryouko.imsb.nrc.ca
Phone: +1 613 993 0880
EMail: wmaton@ryouko.imsb.nrc.ca