Cant setup rDNS.

Hello there team, I have changed my droplet name according to the hostname, but still i cant see any changes,it seems rdns not working

output of host command: Host not found: 3(NXDOMAIN)

Regards, Jinay

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.


Reverse DNS (PTR) records are automatically created based on the name that you give your Droplet in the Control Panel. If you want to rename a Droplet, go to its page in the Control Panel, click directly on the existing Droplet name, and enter a new name there.

There are a few things to keep in mind:

  1. The Droplet name has to be a fully-qualified domain name. This means that a name like “” will generate a valid PTR record, but a name like “centos-s-1vcpu-1gb-nyc3-01” will not generate a PTR record.

  2. If you’re using IPv6 on your Droplet, a PTR record will only be generated for the first IPv6 address assigned to the Droplet, not all 16 IPv6 addresses which are available to the Droplet.

  3. If you have assigned a Floating IP address to your Droplet, a PTR record will only be generated for the original assigned public IPv4 address and not the Floating IP address

Hope, this helps a bit.

Cheers, Sri Charan

Hello, @universaldehgam

The Reverse DNS is configured automatically from our end based on the droplet’s hostname.

The PTR should be automatically adjusted in few hours due to DNS cache. If this is still not working after several hours, you can contact our support team as well.

For managing DNS records from DigitalOcean Kubernetes Using ExternalDNS you can check this tutorial:

Hope this helps.

Regards, Alex