[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#119773: More info [Temp fix]



Mika Tiainen wrote:

[I cc'd debian-ipv6@lists.d.o incase someone there wants to add something]

[CUT]

Changing back ip6.arpa to ip6.int fixes the problem but then Im
concerned about other questions.


IMHO this is the best thing to do for now as ip6.arpa isn't ready for
use yet.


IMHO is not completly true:

fabbione@gundam:~$ 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

and we are supporting both.



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.



As RFC 3152 says:

[CUT]




This is already an ongoing process. It works perfectly for me.



Thanks
Fabbione

--
Debian GNU/Linux Unstable Kernel 2.4.9
fabbione on irc.atdot.it #coredump #kchat | fabbione@fabbione.net



Reply to: