We'd like to use floating IPs to seamlessly move traffic from one droplet to another when re-deploying services.
However, we also aim to support IPv6 and already receive a lot of traffic via v6.
As floating IPs are IPv4 only, this severely limits their ability to achieve their purpose in our scenario, forcing us to rely on slowly propagating DNS updates for a growing portion of our incoming traffic.
Â
Pleas add floating IPv6 Addresses.
This should be merged into the more adopted https://ideas.digitalocean.com/ideas/DO-I-1010
Attachments Open full size
This idea duplicates DO-I-1010#
Attachments Open full size
This would be a great addition indeed
Attachments Open full size
I recently happened upon a use case for this. IPv6 can't live to its potential without this feature.
Attachments Open full size
Lack of IPv6 on floating IPs takes away a lot of the advantages.
Attachments Open full size
I am a Chinese user who deploy v2ray service on a DigitalOcean droplet. The fucking GFW remembers the IP of my droplet and then blocks that IP. Recently (2019-06-05), I have discovered that an IPv6 address lives for about 1 month, but an IPv4 address is almost unreachable. So, a floating IPv6 address can keep the accessibility of my service.
Attachments Open full size
Is this feature anywhere on the roadmap? I know it doesn't have a ton of votes, but being either or with floating IPs and IPv6 kind of hobbles both features.Â
Attachments Open full size
This seems like a no-brainer. Whether using this for load-balancing or failover planning, two uses that DO say floating IP's are suited for, your choices will either be to abandon ipv6 or not rely on the floating IP.Â
Attachments Open full size