John, Congratulations to you and ICANN for this significant step, at all the various layers and meanings of significant. :) 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? 2. Is there any hope that axfr could be permitted in the future? Of course, if you're not the right person to ask feel free to redirect me. Best regards, Doug On 02/16/2011 13:00, John Curran wrote:
Apologies for cross-posting, but I believe this relevant to the NANOG operator community. FYI, /John
Begin forwarded message:
From: ARIN<info@arin.net<mailto:info@arin.net>> Date: February 16, 2011 3:53:38 PM EST To:<arin-announce@arin.net<mailto:arin-announce@arin.net>> Subject: [arin-announce] IN-ADDR.ARPA Zone Transfer Complete
Today ARIN and ICANN are jointly working on the transition of the technical management function for the IN-ADDR.ARPA zone from ARIN to ICANN. ARIN carried out the DNS zone maintenance function for IN-ADDR.ARPA since 1997 and worked closed with ICANN throughout the transition period.
Immediately upon transfer to ICANN, the IN-ADDR.ARPA zone will also be signed using DNS Security Extensions (DNSSEC), providing end-users with the ability to validate answers to reverse DNS queries. The IN-ADDR.ARPA zone is also in the process of being moved from twelve root servers to dedicated nameservers operated by the five Regional Internet Registries (RIRs) and one operated by ICANN.
For more details on the history of this transition please see<http://in-addr-transition.icann.org/>.
Regards,
Communications and Member Services American Registry for Internet Numbers (ARIN)
-- 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/