Yesterday's Windows update causes IPv4 to be default

[Dan Wing]

> -----Original Message-----
> From: ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de [mailto:ipv6-
> ops-bounces+dwing=cisco.com at lists.cluenet.de] On Behalf Of Dick Visser
> Sent: Friday, November 16, 2012 6:58 AM
> To: Sander Steffann
> Cc: Mike Jones; Tassos Chatzithomaoglou; Gert Doering; Dan Wing; ipv6-
> ops at lists.cluenet.de
> Subject: Re: Yesterday's Windows update causes IPv4 to be default
> 
> On 16 November 2012 15:04, Sander Steffann <sander at steffann.nl> wrote:
> 
> > Since they charge $3k when you enable it + add $3k to your monthly
> > bill for having it enabled I doubt that many customers would be happy
> > with that... (the numbers are what I heard from one Akamai customer,
> > they might vary)
> 
> My intern is looking into IPv6-only-izing VMware, but ran into issues
> with software updating, because 'hostupdate.vmware.com' sits in Akamai
> and has only IPv4.  Somehow I think I found the reason why :)

Seems a perfect reason to drop in a NAT64 so the IPv6-only host can
visit hostupdate.vmware.com.

-d