[137546] in North American Network Operators' Group
Re: [arin-announce] IN-ADDR.ARPA Zone Transfer Complete
daemon@ATHENA.MIT.EDU (Joe Abley)
Wed Feb 16 17:24:46 2011
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <4D5C420C.6030306@dougbarton.us>
Date: Wed, 16 Feb 2011 17:23:30 -0500
To: Doug Barton <dougb@dougbarton.us>
X-SA-Exim-Mail-From: jabley@hopcount.ca
Cc: John Curran <jcurran@arin.net>, NANOG <nanog@merit.edu>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hi Doug,
On 2011-02-16, at 16:30, Doug Barton wrote:
> Relevant to another post today, I've noticed that neither the =
*.ip6-servers.arpa nor the *.in-addr-servers.arpa allow axfr. Which =
leads to the following questions:
>=20
> 1. Was that a conscious decision, and if so why?
It's a question for the individual operators of the servers. I can only =
speak for the particular servers that ICANN operates.
ICANN operates B.IN-ADDR-SERVERS.ARPA and B.IP6-SERVERS.ARPA. As with =
L-Root, we don't permit zone transfers from the servers themselves; our =
goal with the nameservers themselves is to provide them with as much =
headroom as possible for answering DNS queries, and it has never seemed =
to us that also responding to AXFR is going to help with that.
We do however support open zone transfers for the root zone, ARPA, =
IN-ADDR.ARPA and IP6.ARPA from two locations for anybody who cares to =
use them:
xfr.lax.dns.icann.org
xfr.cjr.dns.icann.org
The availability of these servers for AXFR is documented at =
<http://dns.icann.org/services/axfr/>.
Joe=
