How to really set up reverse DNS for a droplet.

In order to have one’s emails processed correctly, a valid reverse DNS entry is needed. Supposedly, a reverse DNS entry is automatically created using the name that is given to a droplet, and when you change it, the new name is associated with the IP address. In doing an “nslookup” on the IP address for my droplet, the following message is displayed:

** server can’t find NXDOMAIN

I do have my own DNS servers where foreward DNS for the droplet resides. What is the correct way to have a valid reverse DNS entry created?

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.

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.

Are you sure you’re doing the NS Lookup correctly?

Here’s an example:

Default Server:

> set type=PTR
Non-authoritative answer:
Address:     name =

As you can see, I do this:

set type=PTR

EDIT I didn’t really answer your question, did I?

If you did the lookup correctly, and the PTR isn’t reflecting for that IP address, it will either be due to your DNS caching server, or an issue at DO. If you’re sure it’s not working (check here), open a ticket with DO support.