I cannot use this service for our legitimate email servers without floating IP + reverse DNS. It seems that, in order to block spammers, you are also blocking legitimate businesses. The right thing to do would be to find another way to block spammers.

I have been fighting spammers for 15 years. Cloud computing was a godsend for them. The latest tactic is to spin up a few servers, send out a bunch of spam on fresh IPs, then make them disappear. I’ve been fighting one spammer for 10 months who has used over 300 ranges of IPs and counting. This tactic you have of not allowing reverse DNS for floating IPs is not stopping a spammer that uses IPs for one day. It is stopping legitimate businesses that want to establish a long term reputation of credibility on a certain IP, something that spammers do not want to do. You are hurting and not helping.

Come on, this can’t be hard. Reverse lookup of a floating IP is important.

Where is Digital Ocean????
An ETA or a work around would be the least to do for something that is asked/needed so much.

+111 - We stopped receiving email. Why - cause we were blacklisted as our floating IP / DNS record did not match sending servers IP. Floating IP useless!

Really? SINCE FUCKING 2015 ASKING THIS!

+100

I really don’t like obscenities in public conversations, but vagkaefer has a point.

+100

Just keeping this thread going in the hopes it it get picked up

+1

+1000

Hey friends!

Just wanted to weigh in on this a bit. Currently adding and removing a floating IP from your account is difficult for us to track. This means that allowing SMTP would benefit spammers greatly, further hurting the function for legitimate customers. That isn’t your problem of course, but it is meant to show the depth of work that must be done around this before we could consider unblocking SMTP, which is the function that drives the need for a PTR record. Dealing with the use of our network by spammers continues to be a daily fight.

Please know that we do read your feedback and we do use it to inform our discussions around changes to the platform. While we make no promises, your feedback does serve a function and it is to advocate for the change that you request.

Always keep the feedback coming, we are continually thankful for it <3

Jarland

It is important to activate this service. Possibility to add a hostname in any floating ip

+1000 This really needs to be done. It makes floating IP’s completely useless for mail servers. Frustrating!

Please give us the option for setting PTR on floating IPs.

+10000 We really need this feature enabled, it’s really important for our business!!! Please do it asap or you guys will lose lots of genuine clients!

+1 to this.

I have another use case:

Let’s say that I’m using CloudFlare for whatever reason, for my site. If I use my main IP for mail, then I’ve revealed my main IP, defeating the purpose of CloudFlare. However, if I use a floating IP for mail, I now have insulation on the mail end for my main IP. If I get attacked on mail.myhost.net, I can just detach the floating IP, and my main site will continue unaffected.

This, however, won’t work without PTR records for floating IPs, as mail won’t work properly without forward and reverse resolving matching each other.

Unfortunately PTR records are not currently supported for Floating IPs.

+1

I too would like to see this, as others have said having a reverse lookup of the IP is important, especially when sending emails.

+1 …?

+1

I’m running a couple of mail servers and I REALLY need this feature!

+1
would be really nice

PTR Needed for floating IPs attached to a MX machine.

This is available from other cloud providers.

A bit of a problem for us that there isn’t any way to do this with DO…

+1

+1 :)

+1

+1

+1

It seems Gmail is no longer accepting emails from a server without a valid PTR, which you cannot get with a floating ip at DigitalOcean, so you either have a PTR or have the failback options offered by the floating ip, but not both. What a shame.

+1

digital ocean is not usable for my system without floating IPs, and floating IPs are not usable without PTR

Looks like this issue is open for a year and a half now, can anyone at Digital Ocean address it?

+1

+1

+1

+1

+1

+1

+1 When will this be available? This is an issue.

When will this be addressed, if at all? It’s been almost two years since the only official response here. Can we please at least get someone from DO to respond here with whether or not this is even in the pipeline for implementation sometime?

+1

+1 Need PTR for Floating IPs too. all the major MX servers are rejecting our emails from all our domains on more often, due to PTR not matching with our floating ip.

+1

+1 Trying to use this for flexibility but PTR is a must for public domains.

+1 :-)

+1

+1

+1

I REALLY need this feature!!

+1

+1

+1 as well

+1

This is a major overlook and a dissapointment, I require stable PTR records for mail services.

+1

Hi Jarland,
Thank you for the reply and for finally giving a reasonable explanation on the rationale behind the decision to not allow PTR records.

Judging by the activity on this thread I’m sure you agree this is quite a serious issue for Digital Ocean’s customers so I hope the DO team can implement the IP tracking required and enable PTR records as soon as possible so we can finally use this potentially great feature.

Please keep us up to date with the progress and hopefully the DO team wont leave it another 3 years before responding as this can be quite disconcerting for those of us that do like to provide feedback.

+1

+1

+1 I need this for 4 servers

+1

I really need this feature. Half of my emails are being rejected because of it…

To set the PTR for a Floating IP, please do the following:

• Log into digital ocean account
• Click droplets
• Click the droplet you want to set the PTR record
• Click on the name to edit it and rename it
• Enter your FQDN
• Save & done!

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 the 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.

Hoping for a solution. Everything else is spot on!

I’m planing to upgrade my hosting infrastructure so, to minimize the impact I’m planing to migrate all dns records to foating IP’s and the simply reasign the floating IP (Like amazon aws let you do).
If I can’t create PTR records this became unusefull.