Existing PTR Records Not Found - rDNS Failure

  • Thread starter MicrosoftSuperFanMan
  • Start date
M

MicrosoftSuperFanMan

At first I thought my hosting company had failed to add a rDNS entry for my IP address but now I don't know what to think. I have an A record with a corresponding PTR record but whenever I check the IP for a PTR on MxToolBox or anything else it cannot be found.

The A record in the copblaster.com forward lookup zone has the following values:

Name: server, Type: Host A, Data 185.164.72.225

The Reverse Lookup Zone 72.164.185.in-addr.arpa has the following PTR record:

Name: 185.164.72.225, Type: PTR Data: server.copblaster.com


To make sure there is no conflict with other PTR records I deleted the rest. I had been creating PTR records automatically whenever adding an A record. Now there is only one PTR record, it matches the hosting company record exactly, but it is never found. The hosting company even sent me a screenshot as proof that they added the record. The above records is all I needed to add on my end with my last host but that host used Windows Server 2012 not 2016.

Continue reading...
 
Back
Top Bottom