Re: Office 365 broken on ipv6

2013-04-30 Thread Bernhard Schmidt
Nick Hilliard wrote: > 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 2

RE: Office 365 broken on ipv6

2013-04-30 Thread Christopher Palmer
This is being esclated. -Original Message- From: Hibler, Florian [mailto:florian.hib...@kaiaglobal.com] Sent: Tuesday, April 30, 2013 4:38 AM To: nanog@nanog.org Subject: Re: Office 365 broken on ipv6 Hi, seems at least one box got fixed: dyn-10-0-2-50:~ local_fhibler$ telnet -6

Re: Office 365 broken on ipv6

2013-04-30 Thread Hibler, Florian
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 re

Re: Office 365 broken on ipv6

2013-04-30 Thread Jima
On Tue, April 30, 2013 10:33 am, Nick Hilliard wrote: > 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...

Re: Office 365 broken on ipv6

2013-04-30 Thread Charlie Allom
On Tue, Apr 30, 2013 at 11:33:41AM +0100, Nick Hilliard wrote: > https://outlook.office365.com does not work on ipv6; looks like this has > been broken for some while. Not one host in the RING says it is up: https://spodder.com/p/ByYYcAomOxawsZRPme74X9pG via https://ring.nlnog.net/ C. -- +

Re: Office 365 broken on ipv6

2013-04-30 Thread Jared Mauch
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

Re: Office 365 broken on ipv6

2013-04-30 Thread Sasa Ristic
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 addr

Re: Office 365 broken on ipv6

2013-04-30 Thread Aftab Siddiqui
Quite Interesting... from Europe, using ipv6, it seems to be working: > --- > 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@stingra

Re: Office 365 broken on ipv6

2013-04-30 Thread Sasa Ristic
from Europe, using ipv6, it seems to be working: --- master:~$ telnet -6 outlook.office365.com 443 Trying 2a01:111:f400:800::6... Connected to ipv6.exchangelabs.com. Escape character is '^]'. --- On Tue, Apr 30, 2013 at 12:33 PM, Nick Hilliard wrote: > https://outlook.office365.com does not

Office 365 broken on ipv6

2013-04-30 Thread Nick Hilliard
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 r