By vsnb
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
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Accepted Answer
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.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.