THIS SERVICE HAS NOT BEEN IN USE SINCE 2005. MOVE ALONG.

AS112 running on marla.ludost.net currently servicing Lirex Net and customers

Powered by: ISC BIND 9, zebra bgpd, iptables/netfilter, perl, rrdtool, Apache, debian gnu/linux, not to mention ethernet and cheap PC hardware and even electricity
Implemented and maintained by: Boyan Krosnov

AS112 FAQ (in Bulgarian)
Statistics
Recent updaters(abusers)

For more information about this page contact the admninistrator at as112ludost.net

This is a local copy of the original http://as112.net/ page:

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 and other ambiguous addresses, as follows:

10.0.0.0/8
172.12.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.

IPv4 Anycast

As a way to distribute the load for RFC1918-related queries, we use IPv4 anycast addressing. The address block is 192.175.48.0/24 and its origin AS is 112. This address block is advertised from multiple points around the Internet, and these distributed servers coordinate their responses and back end statistical analyses.

RFC1918 Server Operators

Each such server also has a well known unicast address for diagnostic purposes:

Internet Software Consortium 204.152.184.191 Note: this is also the stealth primary master for the zones
VeriSign Global Registry Services 65.199.34.211 65.199.34.212
Autonomica 192.36.144.115
WIDE 202.13.183.34

Well known addresses

The well known addresses for authoritative name service for zones associated with RFC1918 PTR queries are:

192.175.48.1
listed in SOA RR, receives mostly updates
192.175.48.6
listed in NS RR, receives mostly queries
192.175.48.42
listed in NS RR, receives mostly queries

Client side operations

To find out which actual server is responding to your anycast queries, use the UNIX dig command, as in:

	dig @prisoner.iana.org hostname.as112.net any

The response should look something like this:

	;; ANSWER SECTION:
	$ORIGIN hostname.as112.net.
	@ 15S	TXT	"Internet Software Consortium, Inc." "Palo Alto, CA, USA"
		TXT	"See http://as112.net/ for more information."
		NS	blackhole-1.iana.org.
		NS	blackhole-2.iana.org.
		SOA	hazel.isc.org. hostmaster.isc.org. (
			2002050100	; serial
			1H		; refresh
			10M		; retry
			4w2d		; expiry
			15S )		; minimum

Where the SOA RR MNAME tells the host name of the answering anycast server, the SOA RR ANAME tells the e-mail address of the server's administrator, and some unordered TXT RR's tell other information which may be of interest. (Note: the whole response must fit in a 512 octet DNS/UDP datagram.)

Hosting

To arrange to host anycast service for these zones, contact the AS112 Project. You should know how to configure both intra-AS routing, and inter-AS routing using BGP, and you should plan on running a stealth slave of the IANA.ORG zone so that your servers will return appropriate glue in their responses.