On Mon, 19 Nov 2001, [EMAIL PROTECTED] wrote: >> IMHO this is the best thing to do for now as ip6.arpa isn't ready >> for >> use yet. > > IMHO is not completly true: > > [EMAIL PROTECTED]:~$ host -t NS ip6.arpa > ip6.arpa NS ARROWROOT.ARIN.NET > ip6.arpa NS NS.EU.NET > ip6.arpa NS NS.RIPE.NET > ip6.arpa NS NS.APNIC.NET > ip6.arpa NS BUCHU.ARIN.NET > ip6.arpa NS SVC00.APNIC.NET
Oh, they weren't there yet when I made the original report :) But those only include 2001::/16 not the current 6BONE (3ffe::/16) and I guess they never will as we are moving to "official" allocations now? Then I would agree that ip6.arpa is okay but would still like to see ip6.int as a backup especially if the 3ffe::/16 zones aren't moving to ip6.arpa. >> Checking both of them would probably be the best solution but that >> should be a upstream decision and maybe discussed on some of the >> ipv6-related lists. Until that is done ip6.int is the one that >> should be used. > > I agree 100% but I was unsure how to write the patch for various > reasons. The first one is that Im not skilled enough (but try does > not cost anything) and second one I was worried about the way in > which they changed code in the upstream. They had simply switched > from ip6.int to ip6.arpa without modifing other portion of the code. > I got the idea that the ip6.arpa was not working for other reasons > (probably the code to pool the dns needs to be reviewed). I did a > simple traceroute6 and I noticed that my dns'es were not polled by > anyone in that moment. It seems that most providers haven't configured their servers for the now zones yet, I got a lame delegation for every ip6.arpa zone that I tried :( -- Mika Tianen Always be wary of any helpful item that [EMAIL PROTECTED] weighs less than its operating manual. http://mikat.iki.fi -- (Terry Pratchett, Jingo)
