This will be the last mail to everyone because I think we are running a bit off topic from the original "bug".
Mika Tiainen wrote:
[CUT]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 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?
The only reason why you didn't found them is because in the report you where using 2.2.4-5 that were completly broken. In 2.2.4-6 that came out
yesterday (atleast I found them yesterday) ip6.arpa was working.
Anyway I have 3ffe:blabla addresses and I am resolved. The only things
I noticed is that one root server was downloading the zone from my dns server. In the first instance I was blocking arbitrary download of the zones and I was not able to resolv. After some tcpdump activities I noticed a zone transfer request from one of the root server so I tryed to leave it open and after a while everything was working fine.
Just try that. It might fix all your problem.
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 :(
Yes that's only because isp need to use bind9 or higher in order to have
ip6.arpa working. bind8 does not support it at all and sometimes the upgrade to bind9 is not that painless.
Cheers Fabbione
-- Debian GNU/Linux Unstable Kernel 2.4.9 fabbione on irc.atdot.it #coredump #kchat | [EMAIL PROTECTED]
