[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

MSFT reverse IP failure?

Subject: MSFT reverse IP failure?
From: list at satchell.net (Stephen Satchell)
Date: Mon, 26 Feb 2018 16:09:00 -0800
In-reply-to: <CY4PR21MB0181827F68709607C5C14084B2C10@CY4PR21MB0181.namprd21.prod.outlook.com>
References: <[email protected]> <CY4PR21MB0181827F68709607C5C14084B2C10@CY4PR21MB0181.namprd21.prod.outlook.com>

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 at microsoft.com

References:
- MSFT reverse IP failure?
  - From: math at sizone.org (Ken Chase)
- MSFT reverse IP failure?
  - From: chkuhtz at microsoft.com (Christian Kuhtz)

Prev by Date: MSFT reverse IP failure?
Next by Date: MSFT reverse IP failure?
Previous by thread: MSFT reverse IP failure?
Next by thread: MSFT reverse IP failure?
Index(es):
- Date
- Thread