I'm loving that you have Floating IPs now and I'd like to setup reverse lookups (PTR) for them.
Can't fully use floating IP feature without reverse DNS lookup.
The floating IP is a great thing.
Without the ability to assign a PTR record it's not so great.
Just found out that Public IP doesn't support rDNS. Not too happy! No wonder we're having deliverability issues. Come on guys, let's get this sorted out.
Strong support for this. PTR records for floating IPs should have been offered from the start. Can't use floating IPs without this.
This is super important if we want move to using floating ips!
This is a requirement for anybody using their droplets for serious mail handling.
Also, as others have pointed out, it would be extremely important having the ability to "elevate" the old anchor IP address to the rank of floating Ip address: it could have taken years to attain a reasonable "trust" of your IP address from xBL services. Starting anew with the newly assigned floating IP address would be a royal pain in the back, so please implement the functionality to "swap" anchor/floating IP addresses...
reverse dns is a must for floating ips. Can not reliably send mails without it
Seems like an obvious omission
PTR as well as outgoing routing.
Please mark this as urgent. It is almost plain silly that this is missing.
And I really dislike to whole "just log it on UV" attitude from the helpdesk
It is almost like nobody is thinking anymore
The best idea's do NOT come in numbers!
How about everyone sends the link to this request *again* => to the support desk? I agree with Tom who says "don't underestimate the importance due to lower votes"
Not all great and simple ideas are concencus or high vote based ..... actually none of them
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?
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 126.96.36.199
Jul 20 11:23:03 myserver postfix/smtpd: connect from unknown[188.8.131.52]
Jul 20 11:23:03 myserver postfix/smtpd: NOQUEUE: reject: RCPT from unknown[184.108.40.206]: 450 4.7.1 Client host rejected: cannot find your hostname, [220.127.116.11]; from=<email@example.com> to=<firstname.lastname@example.org> proto=ESMTP helo=<server.mydomain.tld>
Jul 20 11:23:03 myserver postfix/smtpd: disconnect from unknown[18.104.22.168]
* Note: all IP addresses, e-mails and hostnames has been changed.
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?
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.
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.
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!
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.
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.
Can't send mail with no ptr!
Add PTR for Floating IP address as well, and also be apple to controll the PTR segment for the actual VM..
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).
Thanks for the feedback. Could you let us know your use case?
This is pretty critical if your floating ip has an email server behind it.
You won't be notified about changes to this idea.