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