www.microsoft.com

[danclark]

Hey,

Anyone having problems hitting www.microsoft.com today via the HE TB?

Tracing route to ipv6-selector.www.ms.akadns.net [2a01:111:2004:3::13]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2001:470:xxxx
  2    23 ms    22 ms    22 ms  xxx-1.tunnel.tserv5.lon1.ipv6.he.net [2001:
470:xxx]
  3    16 ms    21 ms    24 ms  gige-g4-8.core1.lon1.he.net [2001:470:0:67::1]
  4    16 ms    16 ms    16 ms  2001:7f8:4::1f8b:1
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7   106 ms   112 ms   107 ms  2a01:111::9b
  8     *        *        *     Request timed out.
  9   158 ms   158 ms   158 ms  2a01:111::e8
10   177 ms   158 ms   176 ms  2a01:111:0:2::56
11     *        *        *     Request timed out.
12  Destination net unreachable.

Yet face:b00c works fine:

Tracing route to www.facebook.com [2a03:2880:2110:3f03:face:b00c::]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2001:470:xxx
  2    21 ms    22 ms    22 ms  xxx-1.tunnel.tserv5.lon1.ipv6.he.net [2001:
470:xxx]
  3    38 ms    18 ms    24 ms  gige-g4-8.core1.lon1.he.net [2001:470:0:67::1]
  4    90 ms    90 ms    90 ms  2001:7f8:4::80a6:1
  5    90 ms    90 ms    90 ms  xe-3-3-0.bb02.iad2.tfbnw.net [2620:0:1cff:dead:b
eef::24d]
  6    99 ms   104 ms    99 ms  ae9.bb02.frc1.tfbnw.net [2620:0:1cff:dead:beef::
d6]
  7   114 ms   100 ms    99 ms  ae2.dr02.frc1.tfbnw.net [2620:0:1cff:dead:beef::
9b]
  8    99 ms   100 ms    99 ms  2620:0:1cff:dead:beee::163
  9   100 ms    99 ms    99 ms  www6-slb-12-03-frc1.facebook.com [2a03:2880:2110
:3f03:face:b00c::]

Trace complete.


Yet ultratools (and others) traceroute fine online. Odd.

[cholzhauer]

I'm able to ping or traceroute, but HTTP traffic seems to get through with no problem

[danclark]

Interesting, thanks for the reply. I can't hit the servers on HTTP - only if I fallback to IPv4.

Looking at the he.net tools, it seems the traceroute has the same problem. Odd.

[kasperd]

Oh the irony. Microsoft invented Teredo. Teredo relies on the fact that IPv6 requires hosts to respond to ICMPv6 echo requests. A Teredo client cannot contact a host that does not respond to ICMPv6 echo requests. The Teredo tunnel setup protocol sends an ICMPv6 echo request to the server. A Teredo client won't send the TCP SYN packet until it has received the ICMPv6 echo reply.

And now Microsoft have put up a webserver that won't respond to ICMPv6 echo requests. Making their own webserver incompatible with the tunnel protocol, which they invented is quite the move.

But it looks like they pulled the AAAA record again. I get no AAAA records when I try to look up www.microsoft.com. I tried using two different DNS servers.