MSFT reverse IP failure?
hank at efes.iucc.ac.il
Tue Feb 27 07:38:10 UTC 2018
On 27/02/2018 01:25, Christian Kuhtz via NANOG wrote:
126.96.36.199/32 should reverse to |
*Optional:* Remote Connectivity Analyzer
<https://testconnectivity.microsoft.com/> - Initiate connectivity tests.
TCP 80 & 443
> A little difficult to say what this without knowing what 188.8.131.52 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
> -----Original Message-----
> From: NANOG <nanog-bounces at nanog.org> On Behalf Of Ken Chase
> Sent: Monday, February 26, 2018 1:31 PM
> To: nanog at 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[184.108.40.206]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, [220.127.116.11];
> NetRange: 18.104.22.168 - 22.214.171.124
> CIDR: 126.96.36.199/13, 188.8.131.52/14, 184.108.40.206/11
> NetName: MSFT
> A bit of an oversight?
More information about the NANOG