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
etc

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

+1 to this. Being able to set the individual ipv6 pointers would be very nice.

yes, i know that you guys will only give us one IPv4 address per droplet, but we can also have one or more IPv6 addresses per droplet. we might not want the same PTR record for each of these IPs though. give us more control please so that we can set individual PTR records for each IP on each droplet (e.g. if there is one IPv4 address and five IPv6 addresses on a droplet, please let us individually set all six PTR records to whatever we want instead of just automatically setting them all to the same thing).

thanks

otherwise at the very least, make a feature to let us have the authority to run BIND or something on a droplet and set up our PTR records that way if it is easier for you to code

DO would be perfect for me if it had this feature.

I'm having this issue with my droplet - I want to add PTR records to the other ipv6 addresses. Tunnel Broker won't work properly for me as well.

Still wish this was possible... Setting multiple IPv6 PTR records is a feature on so many other providers, why not DigitalOcean? It is the one thing that keeps DO from being perfect for me.

This is required in order to support smtpd restrictions based on AAAA <==> PTR mapping. Without being able to set up a reverse mapping, mail sent from an otherwise properly configured droplet will be rejected by MTAs that implement this restriction.

still waiting on this... we need a mechanism to get control of PTRs / FDQNs **INDEPENDENTLY** for each host (ipv4, each ipv6)

Yes will be great, and make more atractive from concurrent virtual hosting company.

I have a WHM/Cpanel server and need to set PTR as rDNS so hotmail.com and others won't bounce emails from the domain

XXXX.ip6.arpa. 1h IN PTR mail.example.com.

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
etc

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

WHY ARE WE STILL WAITING FOR THIS?

Lol, this is fundamental, what is wrong with DO?

If you assign someone 15 addresses you either set all 15 for them or allow them to configure them!

Would love to have this available.

I can only change my PTR record from one FQDN to another, but I cannot delete it if I've set it once. That sucks. Please add that option?

please and yes

Please add this option.