Office 365 broken on ipv6 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 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


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

seems at least one box got fixed:

dyn-10-0-2-50:~ local_fhibler$ telnet -6 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
Escape character is '^]'.

Best regards,

Quite Interesting...

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

<>master:~$ telnet -6 443
Trying 2a01:111:f400:800::6...
Connected to
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 is not resolving to the above address google n he

Aftab A. Siddiqui

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

master:~$ host is an alias for is an alias for has IPv6 address 2a01:111:f400:2c00::6 has IPv6 address 2a01:111:f400:800::6 has IPv6 address 2a01:111:f400:c00::6 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...

FYI: Here's what I'm seeing:

puck:~$ curl -v
* About to connect() to 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
* connected
* Connected to ( 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:
* issuer: CN=MSIT Machine Auth CA 2,DC=redmond,DC=corp,DC=microsoft,DC=com

Not one host in the RING says it is up:



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.


This is being esclated.

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