[137568] in North American Network Operators' Group
Re: [arin-announce] IN-ADDR.ARPA Zone Transfer Complete
daemon@ATHENA.MIT.EDU (David Conrad)
Wed Feb 16 21:17:31 2011
From: David Conrad <drc@virtualized.org>
In-Reply-To: <FD0117FC-A391-43CE-BAAB-35231E206829@corp.arin.net>
Date: Wed, 16 Feb 2011 18:15:36 -0800
To: John Curran <jcurran@arin.net>
Cc: NANOG <nanog@merit.edu>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Congrats to all on getting this done! It's been a long time in coming. =
Good to see it finally finished.
Regards,
-drc
On Feb 16, 2011, at 1:00 PM, John Curran wrote:
> Apologies for cross-posting, but I believe this relevant to the NANOG =
operator community.
> FYI,
> /John
>=20
> Begin forwarded message:
>=20
> 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
>=20
> 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.
>=20
> 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.
>=20
> For more details on the history of this transition please see =
<http://in-addr-transition.icann.org/>.
>=20
> Regards,
>=20
> Communications and Member Services
> American Registry for Internet Numbers (ARIN)
>=20
