Question

New Droplet - PTR resolves to a domain which does not belong to me

Posted October 5, 2016 1.3k views
DNS

Hi,

I’m running a droplet, the current public IP resolves to a domain which belongs to somebody else:

nslookup -type=any 188.166.17.218 ns3.digitalocean.com
Server: ns3.digitalocean.com
Address: 2400:cb00:2049:1::c629:dead#53

218.17.166.188.in-addr.arpa name = basmail.com.

I did not configure DNS which would overwrite the old entry for the shared IP however this is a glitch IMO - PTRs should get cleaned up.

Is there a way to fix this?

cheers

Add a comment
vsnb
By:
vsnb
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

1 answer
eris October 5, 2016

Right now, the PTR for an IP is based on the Droplet’s name, if the Droplet’s name is set to an FQDN. If the Droplet’s name isn’t an FQDN, the PTR may remain set to the last Droplet’s name that used an FQDN.

This is a bug that we’re working on fixing, but it doesn’t affect any functionality. If this bugs you, simply rename your droplet to an FQDN and the PTR will get overwritten.

We also have the ability to clear the PTR manually if you contact support, and we do clear all stale PTRs on a semi-regular basis until we’re able to reliably clear the PTR when an IP is unassigned.

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help