Re: MSFT reverse IP failure?

[Christian Kuhtz via NANOG <nanog () nanog org>]

Hah. Thanks. :)

Yes, it's a big shop..
________________________________
From: Hank Nussbacher <hank () efes iucc ac il>
Sent: Monday, February 26, 2018 11:38:10 PM
To: Christian Kuhtz; Ken Chase; nanog () nanog org
Subject: Re: MSFT reverse IP failure?

On 27/02/2018 01:25, Christian Kuhtz via NANOG wrote:


13.67.59.89/32 should reverse to

testconnectivity.microsoft.com


https://support.office.com/en-us/article/office-365-urls-and-ip-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Foffice-365-urls-and-ip-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2&data=04%7C01%7Cchkuhtz%40microsoft.com%7C8feebbd592e14a66113808d57db50f3f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636553138976621459%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=WD3c6X8izjYwGfu3nNxpcXfmASzC2e6%2FIoqE%2BXa6htY%3D&reserved=0>




Optional: Remote Connectivity 
Analyzer<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftestconnectivity.microsoft.com%2F&data=04%7C01%7Cchkuhtz%40microsoft.com%7C8feebbd592e14a66113808d57db50f3f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636553138976621459%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=vnTCuAez4bQ%2F3o93pF3NwmvgcGSsoaWsRhRHtDiBd5Y%3D&reserved=0>
 - Initiate connectivity tests.


testconnectivity.microsoft.com



no


13.67.59.89/32
40.69.150.142/32
40.85.91.8/32
104.211.54.99/32
104.211.54.134/32



TCP 80 & 443


-Hank


Ken,

A little difficult to say what this without knowing what 13.67.59.89 actually is.   If this is an Azure deployment, 
ReverseFqdn needs to be populated on the Public IP address resource.  Please take a look here 
https://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-for-azure-services<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdns%2Fdns-reverse-dns-for-azure-services&data=04%7C01%7Cchkuhtz%40microsoft.com%7C8feebbd592e14a66113808d57db50f3f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636553138976621459%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=%2BYU%2BiF91CcB6HaHrMLNE4V%2F1kidNOKibGzUD03JZSgw%3D&reserved=0>

Thanks,
Christian


-----Original Message-----
From: NANOG <nanog-bounces () nanog org><mailto:nanog-bounces () nanog org> On Behalf Of Ken Chase
Sent: Monday, February 26, 2018 1:31 PM
To: nanog () nanog org<mailto:nanog () nanog org>
Subject: Re: MSFT reverse IP failure?

Having a client doing a test from the MSFT exchange tools site, which is failing.

NOQUEUE: reject: RCPT from unknown[13.67.59.89]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, 
[13.67.59.89];

NetRange:       13.64.0.0 - 13.107.255.255
CIDR:           13.96.0.0/13, 13.104.0.0/14, 13.64.0.0/11
NetName:        MSFT

A bit of an oversight?

/kc