Yesterday's Windows update causes IPv4 to be default

Phil Mayers p.mayers at
Wed Nov 21 13:02:39 CET 2012

On 21/11/12 11:58, Nick Hilliard wrote:
> On 21/11/2012 01:54, Doug Barton wrote:
>> Oh c'mon, that's just silly. The intermittent problems are almost certainly
>> not the fault of the content end of the system, they are almost certainly
>> on the user end, or somewhere in between.
> I don't know about that.  Anecdotally, I've noticed that my ipv6 transport
> causes fewer problems than random web sites doing stupid things.  E.g.
> losing ipv6 connectivity for a week last year is one which
> comes to mind.

This matches our observations. The (few) problems we've seen have been 
services which advertise AAAAs but don't function correctly.

Handy hint: if you're running ISC bind as a nameserver and have a 
version with RPZ, you can selectively transform such AAAAs into NODATA 
responses for your clients, as a temporary workaround.

More information about the ipv6-ops mailing list