On 21-feb-05, at 20:09, FRLinux wrote:I have started ipv6 with ip6.arpa until i noticed that some sites on the outside world couldn't resolve properly (read, were taking a long time to resolve, it successful) which is why i *had to* use ip6.int as well for our (read, both home and work, since i work in a place which likes ipv6) zone. I am one of these who actually like ip6.arpa much more than ip6.int, it is my own belief that it makes actually more sense. So if tomorrow, someone tells me ip6.int can be safely removed from my DNS, i will be more than happy.
Apparently you don't understand that when your ip6.int delegation is removed your original troubles will reappear.
(Unless the stuff that created the problems has been upgraded to look for ip6.arpa in the mean time.)
There are some more serious issues as well, if they appeared recently.
Bind 9.3.0 removed support for bitstring queries, so if you:
- run BIND 9.3.0 as your caching server, and
- your hosts' resolver libraries send ip6.arpa records in bitstring format, while ip6.int queries are sent in nibbles (e.g., RHL9, maybe others)
.. You'll experience about 30-40 seconds of delay when you try to log on using SSH. Bind 9.2.4 and earlier work fine. Yes, this has been reported to Bind fellows, and closed as "working as designed."
Sigh..
-- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ 6bone mailing list [email protected] http://mailman.isi.edu/mailman/listinfo/6bone
