<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi All,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Recently it came to our attention that Yahoo had some rather severely broken IPv6 on the servers that .za was diverting to. NOTE: I do not know if this situation applies outside of South Africa since I’m not sure which servers Yahoo is redirecting other African users to.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Basically though, they added quad-a DNS records to all of their servers. They then added the v6 addresses to their servers. Only… they didn’t configure their webservers to actually display the pages via IPv6. So, if you browsed via IPv6 their webservers came back with a nice “This page can’t be located” message. Because the IPv6 connectivity itself worked, there was also no fallback to v4.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So, we queried Yahoo via their standard support channels… and received the most bizarre response I have ever seen, that summarized said “We don’t support v6 on the frontend pages yet, we aren’t going to remove the quad-a’s, please tell your users to use ipv4.yahoo.com” <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Now, that’s nothing short of insanity, especially when in our case, you’re talking about telling 40 thousand+ students to use some other address to access Yahoo… <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>At this point I escalated the issue to other people in Yahoo who seemed to have a fair bit more clue, and I’ve been informed that the issue should be resolved by sometime on Monday. But this is a note to anyone using native v6 and getting strange errors back from Yahoo, things are currently broken, and will only be fixed around Monday timeframe.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have to say, kinda disappointed to see this from a company as large as Yahoo who did such a good job in the world v6 day in promoting v6, because this kinda thing really hurts the deployment of IPv6, it makes people scared to move ahead and it’s not what we need. At the same time, to the guys I eventually ended up being able to escalate to and who were helpful and attempted to assist me immediately, my sincere thanks.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Andrew Alston<o:p></o:p></p><p class=MsoNormal>Alston Networks – Owner <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>