Incorrect PTR record returned despite the fact that DNS are setup properly on a Plesk side

Created:

2017-06-22 18:27:52 UTC

Modified:

2017-08-08 13:17:42 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Incorrect PTR record returned despite the fact that DNS are setup properly on a Plesk side

Symptoms

1. Incorrect PTR record for 203.0.113.2 is returned globally: it is set to mail.example.com in Plesk but global search shows different value:

# nslookup 203.0.113.2
name = some.other.site.

However, Plesk name servers return correct value:

# nslookup 203.0.113.2 ns1.example.com
name = mail.example.com.

2. The dig utility shows a name server which returns the incorrect PTR record:

# dig ANY +noadditional +noquestion +nocomments +nocmd +nostats +trace -x 203.0.113.2
113.0.203.in-addr.arpa. 86400  IN      NS      dns.johndoe.com.

Cause

Global DNS records are stored on the provider's side.

Resolution

Contact the provider of the name server shown by the dig utility output (johndoe.com): provider should edit or remove PTR record for 203.0.113.2 that is stored on their side.

Have more questions? Submit a request
Please sign in to leave a comment.