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
I'm loving that you have Floating IPs now and I'd like to setup reverse lookups (PTR) for them.
-- reply above this line --
A request for support has been created and assigned #392755. A representative will
follow-up with you as soon as possible. You can [v̲i̲e̲w̲ t̲h̲i̲s̲ t̲i̲c̲k̲e̲t̲'s̲ pr̲o̲gr̲e̲s̲s̲ o̲n̲l̲i̲n̲e̲].
Your Seb's Space Team,
If you wish to provide additional comments or information regarding the issue, please
reply to this email or [l̲o̲gi̲n̲ t̲o̲ yo̲u̲r̲ a̲c̲c̲o̲u̲n̲t̲] for a complete archive of your support
I want to run DNS servers through loadbalancer that using Floating IP. PTR record is a must to be valid DNS server.
I'm considering moving my yunohost (self-hosted nextcloud) installation away from DO unless I can get PTR records working on a floating IP so I can establish decent mail reputation. (The IPv6 smtp outbound limitation is also killer here; what use is self-hosting if I can't send mail to my friends on Gmail?) There are other ways to reduce spam besides banning upstanding customers from properly using an essential networking function.
More than Tyson said, it's actually been a feature request since October 2015. Five years!
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."
Come on guys, let's make this a reality!
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.
This is pretty critical if your floating ip has an email server behind it.
Thanks for the feedback. Could you let us know your use case?
If you have a mailserver it is critical in todays day and age that forward and backward resolution is the same (and in most cases that the HELO name matches as well).
Add PTR for Floating IP address as well, and also be apple to controll the PTR segment for the actual VM..
Can't send mail with no ptr!
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.
Floating ips are a great idea that are completely useless to me as they can't be used for the PTR record. It would be AWESOME if this was fixed!
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.
I agree, if floating ip is used on a mailserver, and there is no valid PTR there are many receiving servers that will reject the e-mail.
If we cannot define the PTR ourselves, then maybe adjust it to the hostname of the droplet which the floating IP gets assigned to?
This is a snippet from one of our servers logfile, for a tested droplet with floating IP:
Jul 20 11:23:03 myserver postfix/smtpd: warning: hostname server.mydomain.tld does not resolve to address 220.127.116.11
Jul 20 11:23:03 myserver postfix/smtpd: connect from unknown[18.104.22.168]
Jul 20 11:23:03 myserver postfix/smtpd: NOQUEUE: reject: RCPT from unknown[22.214.171.124]: 450 4.7.1 Client host rejected: cannot find your hostname, [126.96.36.199]; from=<firstname.lastname@example.org> to=<email@example.com> proto=ESMTP helo=<server.mydomain.tld>
Jul 20 11:23:03 myserver postfix/smtpd: disconnect from unknown[188.8.131.52]
* Note: all IP addresses, e-mails and hostnames has been changed.
Large overlap with these issues. It is clear floating IP's need to be upgraded. For instance our e-mail is sometimes marked as SPAM because a failign reverse look-up. A shame really.
On every other server we once owned this was normal/basic
@digitalocean This is a request from 2015. How about we make it happen?
You won't be notified about changes to this idea.