[109393] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: IPv6 routing /48s

daemon@ATHENA.MIT.EDU (Nathan Ward)
Wed Nov 19 16:03:05 2008

From: Nathan Ward <nanog@daork.net>
To: nanog list <nanog@nanog.org>
In-Reply-To: <874p234uxg.fsf@mid.deneb.enyo.de>
Date: Thu, 20 Nov 2008 10:02:29 +1300
Errors-To: nanog-bounces@nanog.org

On 20/11/2008, at 4:06 AM, Florian Weimer wrote:

> * Michael Sinatra:
>
>> And it just reinforces the fear that people have against putting AAAA
>> records in DNS for their publicly-accessible resources, especially
>> www.
>
> Won't current Windows clients work just fine in this case?
>
> I have no idea what a fix should look like for some of the non-Windows
> systems I care about, unfortunately.


No, unfortunately broken 6to4 auto-configuration (ie, in Vista, XPSP2,  
when on a non-RFC1918 IP address) breaks, and you get 90s timeouts  
before falling back to IPv4/A.

Works fine most of the time, however when that non-RFC1918 address is  
behind NAT, or some sort of packet filter, then it doesn't work so  
well, and the client does not have a way to detect that reliably.

--
Nathan Ward






home help back first fref pref prev next nref lref last post