<p dir="ltr"></p>
<p dir="ltr">Sent from ipv6-only Android<br>
On Nov 26, 2012 2:59 PM, "Josh Galvez" <<a href="mailto:josh@zevlag.com">josh@zevlag.com</a>> wrote:<br>
><br>
> We are preparing to roll out IPv6 with DNS64/NAT64 to customers, In my testing I've identified services and sites that are broken through this solution. Of course, as I've looked into why, it comes down to IPv4 literals every time. Amazon Instant Video is one major service that is broken.<br>
><br>
> What success have you had at getting Content Providers to move to IPv6 or fix their sites to at least be DNS64/NAT64 friendly? <br>
><br>
> Does anyone know how to contact someone at Amazon that could push this to someone who could fix it?<br>
><br>
> Thanks,<br>
> Josh</p>
<p dir="ltr">Generally I have had very good success in getting folks to fix ipv4 literal issues. Several success cases, Amazon is not one of them. I reached out to them 2 years ago regarding this issue, but I have not followed up with them since and the contact that was reached left the company. <br>
</p>
<p dir="ltr">CB</p>