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 000.000.000.000.in-addr.arpa.: 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?
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!
Are you sure you’re doing the NS Lookup correctly?
Here’s an example:
nslookup
Default Server: 8.8.8.8
Address: 8.8.8.8
> set type=PTR
> 1.2.3.4
Non-authoritative answer:
Server: 8.8.8.8
Address: 8.8.8.8
4.3.2.1.in-addr.arpa name = example.com
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.
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 AI-native businesses
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.