[162686] in North American Network Operators' Group
Re: Office 365 broken on ipv6
daemon@ATHENA.MIT.EDU (Jared Mauch)
Tue Apr 30 08:05:42 2013
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAPVpXLwNzLm1bHCqCL4_pVAd2KmOdpzVY2k1vKqFZQ1ACvP1ww@mail.gmail.com>
Date: Tue, 30 Apr 2013 08:05:23 -0400
To: Sasa Ristic <ristic.sasa@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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:
* subject: CN=3Doutlook.com,OU=3DExchange,O=3DMicrosoft =
Corporation,L=3DRedmond,ST=3DWashington,C=3DUS
* start date: Sep 18 18:53:09 2012 GMT
* expire date: Sep 18 18:53:09 2014 GMT
* common name: outlook.com
* issuer: CN=3DMSIT Machine Auth CA =
2,DC=3Dredmond,DC=3Dcorp,DC=3Dmicrosoft,DC=3Dcom
> GET / HTTP/1.1
> User-Agent: curl/7.27.0
> Host: outlook.office365.com
> Accept: */*
On Apr 30, 2013, at 7:58 AM, Sasa Ristic <ristic.sasa@gmail.com> wrote:
> yes, you are correct... resolved at my local dns:
>=20
> 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
>=20
> 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...
>=20
>=20
> MS should fix this...
>=20
>=20
>=20
>=20
> On Tue, Apr 30, 2013 at 1:45 PM, Aftab Siddiqui =
<aftab.siddiqui@gmail.com>wrote:
>=20
>>=20
>>=20
>> Quite Interesting...
>>=20
>> from Europe, using ipv6, it seems to be working:
>>> ---
>>> <Zarko.Kecic@rnids.rs>master:~$ telnet -6 outlook.office365.com 443
>>>=20
>>> Trying 2a01:111:f400:800::6...
>>> Connected to ipv6.exchangelabs.com.
>>> Escape character is '^]'.
>>> ---
>>>=20
>>=20
>> The IP address you have mentioned is working fine.
>>=20
>> [root@stingray ~]# telnet 2a01:111:f400:800::6 443
>>=20
>> Trying 2a01:111:f400:800::6...
>> Connected to 2a01:111:f400:800::6.
>>=20
>> Escape character is '^]'.
>>=20
>> but outlook.office365.com is not resolving to the above address =
google n
>> he dns.
>>=20
>> Regards,
>> Aftab A. Siddiqui
>>=20
>=20
>=20
>=20
> --=20
> ricky
