nanog mailing list archives
Re: MSFT reverse IP failure?
From: Stephen Satchell <list () satchell net>
Date: Mon, 26 Feb 2018 16:09:00 -0800
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-services
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
Current thread:
- Re: MSFT reverse IP failure? Ken Chase (Feb 26)
- RE: MSFT reverse IP failure? Christian Kuhtz via NANOG (Feb 26)
- Re: MSFT reverse IP failure? Ken Chase (Feb 26)
- Re: MSFT reverse IP failure? Joshua Morgan (Feb 27)
- RE: MSFT reverse IP failure? Jeff Mealiffe via NANOG (Feb 28)
- Re: MSFT reverse IP failure? Stephen Satchell (Feb 26)
- Re: MSFT reverse IP failure? Hank Nussbacher (Feb 26)
- Re: MSFT reverse IP failure? Christian Kuhtz via NANOG (Feb 26)
- Re: MSFT reverse IP failure? Ken Chase (Feb 26)
- RE: MSFT reverse IP failure? Jeff Mealiffe via NANOG (Feb 27)
- RE: MSFT reverse IP failure? Christian Kuhtz via NANOG (Feb 26)