Yahoo and IPv6

Cameron Byrne cb.list6 at
Tue May 10 01:46:47 UTC 2011

On May 9, 2011 6:11 PM, "Owen DeLong" <owen at> wrote:
> On May 9, 2011, at 9:04 AM, Cameron Byrne wrote:
> > On Mon, May 9, 2011 at 8:16 AM, Arie Vayner <ariev at> wrote:
> >> Actually, I have just noticed a slightly more disturbing thing on the
> >> IPv6 help page...
> >>
> >> I have IPv6 connectivity through a HE tunnel, and I can reach IPv6
> >> (the only issue is that my ISP's DNS is not IPv6 enabled), but I tried
> >> run the "Start IPv6 Test" tool at and
> >> it says:
> >> "We detected an issue with your IPv6 configuration. On World IPv6 Day,
> >> will have issues reaching Yahoo!, as well as your other favorite web
> >> We recommend disabling
> >> IPv6<**http%3A//
> >> or seeking assistance in order to fix your system's IPv6 configuration
> >> through your ISP or computer manufacturer."
> >>
> >> What disturbs me is the piece saying "We recommend disabling
> >> IPv6<**http%3A//
> >> ", with a very easy link...
> >>
> >
> > No IPv6 is better than broken* IPv6.
> >
> For production, yes. However, in terms of recommendations to prepare for
> IPv6 day, uh, no... The better recommendation would be to explain the
> exact issue detected and suggest ways for the user to resolve it.

I hope you are not insinuating that ipv6 is not production today, many real
prod sites are ds today :)  If one properly working website fails over ipv6,
they will all fail for that user  (modulo routing table fragmentation). I
would really like the world to treat v6 as real production, and not doing so
is one of the major hurtles to v6 deployment.

Agreed. It would be nice to diagnose and fix, there are web sites for that,
but that is not yahoo's issue or scope to "the masses" who don't know and
should not care about L3 protocols. The only practical solution at scale is
to turn it off at the client to restore service (web page loads ... ).  The
other practical solution, at scale,  is keep v6 off at the server .... which
is, IMHO, worse.


> Owen

More information about the NANOG mailing list