[dns-wg] RIPE - ARIN cooperation when registering signed legacy reverse zones?
B C brettlists at gmail.com
Thu Feb 11 23:27:44 CET 2010
On Wed, Feb 3, 2010 at 12:28 PM, Wilfried Woeber, UniVie/ACOnet <Woeber at cc.univie.ac.at> wrote: > Bill, > > thanks for the pointer to http://www.ietf.org/id/draft-jabley-reverse-servers-01.txt ! > > I feel that my question was not properly worded :-( > > bmanning at vacation.karoshi.com wrote: > >>>>Now 111.131.in-addr.arpa is signed (since September 2009), and currently >>>>registered at dlv.isc.org. Along with the other high-level ARIN reverse >>>>zones, 131.in-addr.arpa is also signed, and >>>> >>>> https://www.arin.net/resources/dnssec/ >>> >>>Looking at this from a slightly different angle (with ERX in mind) ... >>> >>>Excerpt from the above webpage: >>> >>>"Today, delegations under in-addr.arpa are served by servers operated by >>> ARIN and its contractors,..." >>> >>>Seems to indicate that ARIN has the complete and exclusive control over >>>the full (IPv4-) Reverse Tree? If so, what's the situation for IP6.ARPA? > > My reading was or rather is: > > ARIN is managing all zones/master servers for the complete set of 1. level > delegation points *below* in-addr.arpa and ip6.arpa. > > Apologies for still using flawed DNS terminology, maybe, and/or misreading > the quoted paragraph! > Well The sentence on the ARIN web page quoted: "Today, delegations under in-addr.arpa are served by servers operated by ARIN and its contractors" Seems incorrect to me, I think the other RIR's might be surprised to find they are contractors to ARIN. I guess you might regard those bit's of the space that are shared between the RIR's as kind of contracted out in some way but it still seems like a bizarre way of describing it to me. It does seem strange that in-addr.arpa is delegated to the root servers but ip6.arpa is delegated to ICANN but I suspect there is some history and/or a story here :) Brett
[ dns-wg Archives ]