Reverse DNS missing for some hosts
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	Reedy
	Apr 30 2020, 2:09 PM

Description

For example, 2620:0:861:101:10:64:0:71 is mw1276.eqiad.wmnet, but dig/nslookup etc don't tell you this (and you shouldn't need to have the knowlege that 10:64:0:71 -> 10.64.0.71)

Event Timeline

Reedy created this task.Apr 30 2020, 2:09 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 30 2020, 2:09 PM

Reedy removed a project: Traffic.Apr 30 2020, 2:24 PM

colewhite triaged this task as Medium priority.May 5 2020, 4:18 PM

LSobanski added a project: Infrastructure-Foundations.Jan 3 2023, 2:14 PM

Is this report still valid @Reedy ?
All direct and reverse records for the hosts are automatically generated from Netbox nowadays, so this should not happen anymore.

$ dig +short -x 2620:0:861:101:10:64:0:71
ms-be1064.eqiad.wmnet.

@Reedy: ping?

No reply; assuming this is resolved and closing. Please reopen if still an issue.

Reverse DNS missing for some hostsClosed, ResolvedPublicActions

Description

Event Timeline

Reverse DNS missing for some hosts
Closed, ResolvedPublic
Actions