Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
We are building out DNS management which will allow you to manage Domains as well as configure PTR records.
In the meantime we are processing PTR records manually, just open a ticket form the control panel and we'll get it setup for you.
Good to hear! This is an obstacle for many reasons
PTR records are automatically configured to your virtual servers hostname.
it would be great to have more control over PTR records.
IPv4 pointers are set automatically to the droplet's name, and it seems that any IPv6 interfaces you configure for a droplet are automatically set to the droplet name as well.
currently, you can only have one IPv4 IP on a droplet (i think), but you can have multiple IPv6 IPs for a droplet, and so here is where the ability to have individual PTR control would be great.
It would be great to be able to have different PTRs for different IPs on a single droplet, i.e.:
IPv4 IP points to domain1
IPv6 IP2 points to domain2
IPv6 IP2 points to domain3
please implement this somehow or give us the option to delegate authority for the droplet's assigned IPv6 subnet so that we can run BIND (DNS server) on the droplet and manage PTR records ourselves that way
GIVE US THE POWER please
also see the suggestion "allow droplet vps in-addr.arpa records to be CNAME as well as PTR"
You won't be notified about changes to this idea.