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 -- Ken Chase - math@sizone.org Guelph Canada
Which "Exchange tools site" are you referring to? Happy to help get this fixed up. -jeff -----Original Message----- From: NANOG <nanog-bounces@nanog.org> On Behalf Of Ken Chase Sent: Monday, February 26, 2018 1:31 PM To: 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 -- Ken Chase - math@sizone.org Guelph Canada
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-service... Thanks, Christian -----Original Message----- From: NANOG <nanog-bounces@nanog.org> On Behalf Of Ken Chase Sent: Monday, February 26, 2018 1:31 PM To: 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 -- Ken Chase - math@sizone.org Guelph Canada
Im not exactly sure what this is either, the client sent me a screenshot that called itself the "microsoft connectivity analyzer", which had several steps testing deliverability of email to their domain, with the final test of an actual test email delivery failing. /kc On Mon, Feb 26, 2018 at 11:25:59PM +0000, Christian Kuhtz said:
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-service...
Thanks, Christian
-----Original Message----- From: NANOG <nanog-bounces@nanog.org> On Behalf Of Ken Chase Sent: Monday, February 26, 2018 1:31 PM To: 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 -- Ken Chase - math@sizone.org Guelph Canada
On Tue, Feb 27, 2018 at 11:04 AM, Ken Chase <math@sizone.org> wrote:
Im not exactly sure what this is either, the client sent me a screenshot that called itself the "microsoft connectivity analyzer", which had several steps testing deliverability of email to their domain, with the final test of an actual test email delivery failing.
/kc
It's one of the outbound IP addresses for the Microsoft Remote Connectivity Analyzer, as documented here: https://support.office.com/en-gb/article/office-365-urls-and-ip-address-rang... . Your client's mail exchanger is rejecting the test e-mail message because that particular outbound IP address does not have PTR resource record. Interestingly, all of the IP addresses listed do not. Josh
I've escalated this to the team responsible for the tool. Will report back when we have some resolution. Thanks for calling out the issue. -----Original Message----- From: NANOG <nanog-bounces@nanog.org> On Behalf Of Ken Chase Sent: Monday, February 26, 2018 4:05 PM To: Christian Kuhtz <chkuhtz@microsoft.com> Cc: nanog@nanog.org Subject: Re: MSFT reverse IP failure? Im not exactly sure what this is either, the client sent me a screenshot that called itself the "microsoft connectivity analyzer", which had several steps testing deliverability of email to their domain, with the final test of an actual test email delivery failing. /kc On Mon, Feb 26, 2018 at 11:25:59PM +0000, Christian Kuhtz said:
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-service...
Thanks, Christian
-----Original Message----- From: NANOG <nanog-bounces@nanog.org> On Behalf Of Ken Chase Sent: Monday, February 26, 2018 1:31 PM To: 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 -- Ken Chase - math@sizone.org Guelph Canada
On 02/26/2018 03:25 PM, Christian Kuhtz via NANOG wrote:
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 herehttps://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-for-azure-service...
Nope. NetRange: 13.64.0.0 - 13.107.255.255 CIDR: 13.64.0.0/11, 13.96.0.0/13, 13.104.0.0/14 NetName: MSFT NetHandle: NET-13-64-0-0-1 Parent: NET13 (NET-13-0-0-0-0) NetType: Direct Assignment OriginAS: Organization: Microsoft Corporation (MSFT) RegDate: 2015-03-26 Updated: 2015-03-26 OrgName: Microsoft Corporation OrgId: MSFT Address: One Microsoft Way City: Redmond StateProv: WA PostalCode: 98052 Country: US RegDate: 1998-07-09 Updated: 2017-01-28 Comment: For routing, peering or DNS issues, please Comment: contact: Comment: * IOC@microsoft.com
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-rang... *Optional:* Remote Connectivity Analyzer <https://testconnectivity.microsoft.com/> - 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-service...
Thanks, Christian
-----Original Message----- From: NANOG <nanog-bounces@nanog.org> On Behalf Of Ken Chase Sent: Monday, February 26, 2018 1:31 PM To: 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
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
participants (6)
-
Christian Kuhtz -
Hank Nussbacher -
Jeff Mealiffe -
Joshua Morgan -
Ken Chase -
Stephen Satchell