Blackhole DNS servers are Domain Name System (DNS) servers that return a "nonexistent address" answer to reverse DNS lookups for addresses reserved for private use.
Background
editThere are several ranges of network addresses reserved for use on private networks in IPv4:[1]
Reserved private IPv4 network ranges[2] Name CIDR block Address range Number of
addressesClassful description 24-bit block 10.0.0.0/8 10.0.0.0 – 10.255.255.255 16777216 Single Class A 20-bit block 172.16.0.0/12 172.16.0.0 – 172.31.255.255 1048576 Contiguous range of 16 Class B blocks 16-bit block 192.168.0.0/16 192.168.0.0 – 192.168.255.255 65536 Contiguous range of 256 Class C blocks
Reverse DNS queries are used to map IP addresses to domain names. They are PTR queries for subdomains of in-addr.arpa (for IPv4 addresses)[3] and ip6.arpa (for IPv6 addresses).[4] For example, to find the domain name associated with the IP address 203.0.113.22, one would send a PTR query for 22.133.0.203.in-addr.arpa.
Misconfigured hosts[5] often send reverse DNS queries for private addresses to the public DNS. The public DNS cannot meaningfully respond to these queries, since these addresses are reserved for private networks and can't correspond to a single public domain name. Without any mitigation, these queries would put unnecessary load on the in-addr.arpa and ip6.arpa nameservers.[6]
Role
editTo deal with this problem, the Internet Assigned Numbers Authority (IANA) has set up three special DNS servers called "blackhole servers". Currently the blackhole servers are:[7]
- blackhole-1.iana.org (192.175.48.6)
- blackhole-2.iana.org (192.175.48.42)
- prisoner.iana.org (192.175.48.1)
These servers are registered in the DNS directory as the authoritative servers for the reverse lookup zone of the 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 addresses. These servers are configured to answer any query with a "nonexistent address" answer. This helps to reduce wait times because the (negative) answer is given immediately and thus no wait for a timeout is necessary. Additionally, the answer returned is also allowed to be cached by recursive DNS servers. This is especially helpful because a second lookup for the same address performed by the same node would probably be answered from the local cache instead of querying the authoritative servers again. This helps reduce the network load significantly. According to IANA, "the blackhole servers generally answer thousands of queries per second".[8] Because the load on the IANA blackhole servers became very high, an alternative service, AS112, has been created, mostly run by volunteer operators.
AS112
editThe AS112 project is a group of volunteer name server operators joined in an autonomous system. They run anycasted instances of the name servers that answer reverse DNS lookups for private network and link-local addresses sent to the public Internet. These queries are ambiguous by their nature, and cannot be answered correctly. Providing negative answers reduces the load on the public DNS infrastructure.
History
editBefore 2001, the in-addr.arpa zones for the private networks[1] were delegated to a single instance of name servers, blackhole-1.iana.org and blackhole-2.iana.org, called the blackhole servers. The IANA-run servers were under increasing load from improperly-configured NAT networks, leaking out reverse DNS queries, also causing unnecessary load on the root servers. The decision was made by a small subset of root server operators to run the reverse delegations; each announcing the network using the autonomous system number of 112.[9] Later, the group of volunteers has grown to include many other organizations.
An alternative approach, using DNAME redirection, was adopted by the IETF in May 2015.[6][10] DNS zone administrators can redirect queries to AS112 by setting up a DNAME redirection to empty.as112.arpa.[10]
Answered zones
editThe name servers participating in the AS112 project are each configured to answer authoritatively for the following zones:
- For the 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 private networks:[1]
- 10.in-addr.arpa
- 16.172.in-addr.arpa
- 17.172.in-addr.arpa
- 18.172.in-addr.arpa
- 19.172.in-addr.arpa
- 20.172.in-addr.arpa
- 21.172.in-addr.arpa
- 22.172.in-addr.arpa
- 23.172.in-addr.arpa
- 24.172.in-addr.arpa
- 25.172.in-addr.arpa
- 26.172.in-addr.arpa
- 27.172.in-addr.arpa
- 28.172.in-addr.arpa
- 29.172.in-addr.arpa
- 30.172.in-addr.arpa
- 31.172.in-addr.arpa
- 168.192.in-addr.arpa
- For the 169.254.0.0/16 link-local addresses:[11]
- 254.169.in-addr.arpa
- For certain special-use domain names:[12]
- home.arpa
- For unique identification purposes:[6]
- hostname.as112.net
- hostname.as112.arpa
References
edit- ^ a b c Y. Rekhter; B. Moskowitz; D. Karrenberg; G. J. de Groot; E. Lear (February 1996). Address Allocation for Private Internets. Network Working Group. doi:10.17487/RFC1918. BCP 5. RFC 1918. Updated by RFC 6761.
- ^ Y. Rekhter; B. Moskowitz; D. Karrenberg; G. J. de Groot; E. Lear (February 1996). Address Allocation for Private Internets. Network Working Group. doi:10.17487/RFC1918. BCP 5. RFC 1918. Best Current Practice 5. Obsoletes RFC 1627 and 1597. Updated by RFC 6761.
- ^ Domain names - implementation and specification (Report). Internet Engineering Task Force. November 1987.
- ^ Huitema, Christian; Crawford, Matt (July 2000). DNS Extensions to Support IPv6 Address Aggregation and Renumbering (Report). Internet Engineering Task Force.
- ^ Broido, Andre; Hyun, Young; Fomenkov, Marina; claffy, kc (2006-07-05). "The windows of pivate DNS updates". SIGCOMM Comput. Commun. Rev. 36 (3): 93–98. doi:10.1145/1140086.1140098. ISSN 0146-4833.
- ^ a b c J. Abley; W. Sotomayor (May 2015). AS112 Nameserver Operations. IETF. doi:10.17487/RFC7534. RFC 7534. Obsoletes RFC 6304.
- ^ J. Abley; W. Maton (July 2011). I'm Being Attacked by PRISONER.IANA.ORG!. IETF. doi:10.17487/RFC6305. ISSN 2070-1721. RFC 6305.
- ^ "Common questions regarding abuse issues". IANA.
- ^ T. Hardie (April 2002). Distributing Authoritative Name Servers via Shared Unicast Addresses. Network Working Group IETF. doi:10.17487/RFC3258. RFC 3258.
- ^ a b J. Abley; B. Dickson; W. Kumari; G. Michaelson (May 2015). AS112 Redirection Using DNAME. IETF. doi:10.17487/RFC7535. RFC 7535.
- ^ S. Cheshire; B. Aboba; E. Guttman (May 2005). Dynamic Configuration of IPv4 Link-Local Addresses. Network Working Group IETF. doi:10.17487/RFC3927. RFC 3927.
- ^ Pfister, Pierre; Lemon, Ted (May 2018). Special-Use Domain 'home.arpa.' (Report). Internet Engineering Task Force.
External links
edit- The IANA abuse faq which contains information about the blackhole servers.
- AS112 web page
- RSSAC Meeting Atlanta 2002[permanent dead link] Notes describing RFC 1918 network queries impact on the root servers.
- Mailing list for AS112 operators.