Because most answers generated by the Internet's root name server system are negative, and many of those negative answers are in response to PTR queries for RFC1918, dynamic DNS updates and other ambiguous addresses, as follows:
10.0.0.0/8
172.16.0.0/12
169.254.0.0/16
192.168.0.0/16
There are now separate (non-root) servers for these queries, described below.
At present the project requires that participants of the AS112 system must generate and supply a publicly accessible website that displays statistics gathered from the traffic your anycast node attracts. There are several methods to make this work, but so far the one with the least impact on the system is the Measurement Factory's DSC package. DSC has the advantage of being used in a distributed manner and it can also be split functionally into a separate collector and graphing systems.
This what I have done for a CENTOS:
create these config files to enable IPs 192.175.48.1, 192.175.48.6 and
192.175.48.42 on loopback
$ cat /etc/sysconfig/network-scripts/ifcfg-lo:0
# Loopback clone for AS112
DEVICE=lo:0
BOOTPROTO=static
BROADCAST=192.175.48.255
IPADDR=192.175.48.1
IPV6ADDR=
IPV6PREFIX=
NETMASK=255.255.255.0
NETWORK=192.175.48.0
ONBOOT=yes
$ cat /etc/sysconfig/network-scripts/ifcfg-lo:1
# Loopback clone for AS112
DEVICE=lo:1
BOOTPROTO=static
BROADCAST=192.175.48.255
IPADDR=192.175.48.6
IPV6ADDR=
IPV6PREFIX=
Here's a quick set of notes on setting up an AS112 node based on our
experience using FreeBSD 7.1-RELEASE, OpenBGPD 4.4.1 (built from ports),
and BIND9.6.1-P1 (also built from ports).
You don't need a lot of resources to host an AS112 node. Our particular
instance gets about 1000 queries/second and runs as a 256mb guest (30gb
"hard drive") under VMware on a 1.8 GHz quad core core AMD64 system. The
guest "vmware-vmx" process consistently uses less than 20% of a single
core.
These notes make the assumption that your default gateway is a BGP
Server operators are volunteers who offer a route to the well known addresses of
the AS112 servers, either to handle the queries generated by their local user
populations, or to help carry the global traffic load. We intend the list of
operators shown below to be complete and accurate, but that may not be possible.
The F root server operator also runs instances of AS112 servers at certain
sites. Some of these sites are listed here too.
This list will usually be updated once every month, unless an email is sent
to 112 -at- root-servers.org to notify us of a new node. Additionally, updates
are based on queries made to a select number of known route servers, some of
which are listed at Traceroute.org.
AS112 operators are also asked to subscribe to the mailing list described
elsewhere on this website. Note that publicly accessible statistics are
very definitely encouraged. The DSC package is ideal for this.
Note: this list is really a best efforts endeavour, as
the final list at time of writing is not by any means either definitive or
complete.
Joe Abley and William F. Maton Sotomayor have submitted two Internet Drafts to the IETF for dnsops consideration. More at IETF and slides are here. The ID Tracker has a direct pointer to these.
