I was just pointed in the direction of UV after asking about rDNS for floating IPs. Based on the comments of this page it seems like this has been a strongly requested feature since mid September of 2018. That's over a year and a half of the same request. All of these comments are right on point too! "Can't fully use floating IP feature without reverse DNS lookup." "Strong support for this. PTR records for floating IPs should have been offered from the start. Can't use floating IPs without this." "Don't underestimate the usefulness of this due to a low number of votes. People doing this work really need it. The floating IP might be more important than the droplet IP..." "This is a MUST-HAVE feature for any mail related functionality on a server sitting behind the floating ip."

I'm sure you can read back on all the comments too, but I just wanted to reiterate that I agree with every single point here.

Brooke McKim requested everyone to state a use case. EMAIL! We want to be able to offer email services to our clients. As Issac Linder stated, he's looking (or was) looking to move from a competitor to your service because of their issues with rDNS, or lack thereof. Like him, I too have the majority of my sites that are eStores. They each need to send email for invoices and customer communication. I even agree with his last statement. "A large reason for this was not to force my clients to use some other mail alternative for simple server messages."

I agree. I am (or was) looking for alternatives to move from bluehost VPS, in part because of email deliverability and their issue with DKIM records. Now that I have SPF, DKIM and even DMARC set up, gmail still spams the server outbound emails because of the rDNS issue with floating IPs. Pretty much every server I run sends out email, and some are web stores. Makes little sense to move if I server mail doesn't get to the users. A large reason for this was not to force my clients to use some other mail alternative for simple server messages.

I'll echo this; we require this for an application we're developing at the moment and it's far from ideal that we can't set this. AWS require you to fill out a form which generates a ticket, so even being able to change these records by submitting a ticket request would go a long way to help.

This would be a great feature, especially for mail servers. Many mail filters seriously downgrade mail from IPs that don't resolve in reverse. It's also difficult to ensure a clean reputation and keep regular DO IPs off spam block lists, given that they pass between customers frequently. A Floating IP that stays with a customer for years is worth investing in more heavily — a win-win for DO and its customers.

Another vote for PTR record for Floating IPs. This is a MUST-HAVE feature for any mail related functionality on a server sitting behind the floating ip. As previously noted many mail filters flag messages as spam if sender domain doest resolve in reverse. Deliverability, IP reputation, blacklisting can all be impacted by the lack of a proper PTR record. This pertains not just to full blown mail servers, but also apache/ngix, ossec, fail2ban, cron, and various other system related services that rely upon sendmail, postfix, procmail, etc.

Don't under estimate the usefulness of this due to a low number of votes. People doing this work really need it. The floating IP might be more important than the droplet IP since it is THE ONE that exists in DNS for most HA servers.