[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[arin-announce] IN-ADDR.ARPA Zone Transfer Complete
-----BEGIN PGP SIGNED MESSAGE-----
On 02/16/2011 14:23, Joe Abley wrote:
| 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:
|> 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
| The availability of these servers for AXFR is documented
Thanks for clarifying. I almost included "is axfr available from any
other source?" as a 3rd question, but figured that would come out in the
This leads to 2 additional questions:
1. Is the zone available from those 2 locations "the same" as what's
available on the authoritative servers, or is there a lag time between
updates on the auth and the xfr servers?
2. Is there any objection to having those servers listed in publicly
available documentation on how to configure resolvers to slave the root
and related zones?
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (FreeBSD)
-----END PGP SIGNATURE-----