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

  • Posted on October 5, 2016
  • DNS
  • vsnbAsked by vsnb


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

nslookup -type=any Server: Address: 2400:cb00:2049:1::c629:dead#53 name =

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?


Submit an answer

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!

Sign In or Sign Up to Answer

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.

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.