nanog mailing list archives
Re: Office 365 broken on ipv6
From: Jared Mauch <jared () puck nether net>
Date: Tue, 30 Apr 2013 08:05:23 -0400
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=outlook.com,OU=Exchange,O=Microsoft Corporation,L=Redmond,ST=Washington,C=US * 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
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: 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... On Tue, Apr 30, 2013 at 1:45 PM, Aftab Siddiqui <aftab.siddiqui () gmail com>wrote: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-- ricky
Current thread:
- Office 365 broken on ipv6 Nick Hilliard (Apr 30)
- Re: Office 365 broken on ipv6 Sasa Ristic (Apr 30)
- Re: Office 365 broken on ipv6 Aftab Siddiqui (Apr 30)
- Re: Office 365 broken on ipv6 Sasa Ristic (Apr 30)
- Re: Office 365 broken on ipv6 Jared Mauch (Apr 30)
- Re: Office 365 broken on ipv6 Aftab Siddiqui (Apr 30)
- Re: Office 365 broken on ipv6 Hibler, Florian (Apr 30)
- RE: Office 365 broken on ipv6 Christopher Palmer (Apr 30)
- Re: Office 365 broken on ipv6 Sasa Ristic (Apr 30)
- Re: Office 365 broken on ipv6 Charlie Allom (Apr 30)
- Re: Office 365 broken on ipv6 Jima (Apr 30)
- Re: Office 365 broken on ipv6 Bernhard Schmidt (Apr 30)