Office 365 broken on ipv6

Mailman List Mirror (Read Only)
1

https://outlook.office365.com does not work on ipv6; looks like this has
been broken for some while.

Can someone from Microsoft please fix?

crumpet:/Users/nick% telnet -6 outlook.office365.com 443
Trying 2a01:111:f400:1000::9...
telnet: connect to address 2a01:111:f400:1000::9: Connection refused
Trying 2a01:111:f400:8000::2...
telnet: connect to address 2a01:111:f400:8000::2: Connection refused
Trying 2a01:111:f400:9800::6...
telnet: connect to address 2a01:111:f400:9800::6: Connection refused
Trying 2a01:111:f400:9814::12...
telnet: connect to address 2a01:111:f400:9814::12: Connection refused
telnet: Unable to connect to remote host
crumpet:/Users/nick%

Nick

2

from Europe, using ipv6, it seems to be working:

3

Hi,
seems at least one box got fixed:

dyn-10-0-2-50:~ local_fhibler$ telnet -6 outlook.office365.com 443
Trying 2a01:111:f400:400::6...
telnet: connect to address 2a01:111:f400:400::6: Connection refused
Trying 2a01:111:f400:83e::6...
telnet: connect to address 2a01:111:f400:83e::6: Connection refused
Trying 2a01:111:f400:c04::2...
telnet: connect to address 2a01:111:f400:c04::2: Connection refused
Trying 2a01:111:f400:1014::2...
telnet: connect to address 2a01:111:f400:1014::2: Connection refused
Trying 2a01:111:f400:2c16::6...
Connected to outlook-namwest.office365.com.
Escape character is '^]'.

Best regards,
Florian

4

Quite Interesting...

from Europe, using ipv6, it seems to be working:

---
<Zarko.Kecic@rnids.rs>master:~$ telnet -6 outlook.office365.com 443
Trying 2a01:111:f400:800::6...
Connected to ipv6.exchangelabs.com.
Escape character is '^]'.
---

The IP address you have mentioned is working fine.

[root@stingray ~]# telnet 2a01:111:f400:800::6 443
Trying 2a01:111:f400:800::6...
Connected to 2a01:111:f400:800::6.
Escape character is '^]'.

but outlook.office365.com is not resolving to the above address google n he
dns.

Regards,
Aftab A. Siddiqui

5

yes, you are correct... resolved at my local dns:

master:~$ host outlook.office365.com
outlook.office365.com is an alias for
outlook.office365.com.glbdns.microsoft.com.
outlook.office365.com.glbdns.microsoft.com is an alias for
outlook-latam.office365.com.
outlook-latam.office365.com has IPv6 address 2a01:111:f400:2c00::6
outlook-latam.office365.com has IPv6 address 2a01:111:f400:800::6
outlook-latam.office365.com has IPv6 address 2a01:111:f400:c00::6
outlook-latam.office365.com has IPv6 address 2a01:111:f400:1800::6

2a01:111:f400:c00::6 and 2a01:111:f400:1800::6 are not responding to
queries on port 443, the other two (2a01:111:f400:2c00::6 and
2a01:111:f400:800::6) are working...

MS should fix this...

6

FYI: Here's what I'm seeing:

puck:~$ curl -v https://outlook.office365.com/
* About to connect() to outlook.office365.com port 443 (#0)
* Trying 2a01:111:f400:400::2...
* Connection refused
* Trying 2a01:111:f400:2c16::2...
* Connection refused
* Trying 2a01:111:f400:2c2a::12...
* Connection refused
* Trying 2a01:111:f400:83e::2...
* Connection refused
* Trying 2a01:111:f400:c04::9...
* Connection refused
* Trying 2a01:111:f400:16::6...
* Connection refused
* Trying 157.56.239.18...
* connected
* Connected to outlook.office365.com (157.56.239.18) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* SSL connection using SSL_RSA_WITH_RC4_128_SHA
* Server certificate:
* start date: Sep 18 18:53:09 2012 GMT
* expire date: Sep 18 18:53:09 2014 GMT
* common name: outlook.com
* issuer: CN=MSIT Machine Auth CA 2,DC=redmond,DC=corp,DC=microsoft,DC=com

7

Not one host in the RING says it is up:
https://spodder.com/p/ByYYcAomOxawsZRPme74X9pG

via https://ring.nlnog.net/

  C.

8

I brought this up to a contact at Microsoft on 2013-04-03; the
appropriate team was notified, but I guess someone dropped the ball.
Oops.

     Jima

9

This is being esclated.

10

JFYI, it has been like that for weeks now. Sometimes one of the hosts
connects but mostly all IPv6 addresses don't work.

Bernhard