allow Floating IPs to point to load balancers
This would allow me to scale an app seamlessly in real time, instead of needing to carefully time it against DNS cache latency. After playing around with the new Load Balancers for a bit, It seems like an obvious extension. By the way, I'm really pleased with the feature. It seems very polished.
IPv6 for load balancers
So far, load balancers only get an IPv4 and no IPv6. In practice, this means that load balancers cannot be used if you want to provide IPv6 connectivity. I would love to use this feature, but only if IPv6 was made available.
Reserve IP Addresses / Make sure we can keep an IP if we recreate a droplet.
When destroying a droplet there's a 99% chance that you will get your IP back. If someone creates a droplet while destroying/creating a new one and steals your IP, it's a pain, even if the chances are <1%. This 1% is too much for some. An IP is an important number, your server might not be able to send emails if the last IP's user was sending spam through it. Software licenses are also tied to IP sometimes. When I want to rebuild a server (or resize: disk size) I want to make sure that I get my IP back. Please figure out a way so that we don't lose our IP (100% guaranteed) when we destroy/recreate a droplet.
When we have now a traffic limit and must pay for over traffic we really need traffic stats so we can see what we have to pay when traffic is empty and pay traffic begin ;)
Droplet health status in load balancer
Currently there's: doctl compute load-balancer get <id> [flags] However, this is lack of droplet health status. Its hard for me to do a script with 0 downtime without this info. One of the droplet inside the LB need to be healthy before one need to be turned off.
Bandwidth Limit Increase
Migrations are basic part of infrastructure operations today. When doing big migrations like production DB or user files, 2 Gbps is very low limit comparing to 10 Gbps, which is advertised by DO itself. It would be great if that limit could be lifted, for a short period of time or for certain amount of data. I am sure companies using DO would pay to have their data moved few times faster for some fee.
Allow @ CNAME record
I want to 'alias' domains with @ and a CNAME. Now I'm required to use A/AAAA and this prevents me from centralizing IP-configurations.
Let me "name" IP addresses that are allowed to access my firewall so I can easily recognize which ones to add/remove/edit. This would be so awesome!!
Configurable SOA record in DNS
Configurable SOA Records for DNS to change email address.
Allow DO DNS A record (id) in firewall rules and managed database access rules
I would like to add an A record to the rules of my firewalls or Managed Databases. I would prefer and am perfectly happy if that can only be an A record (or even id) from a domain registered within the DigitalOcean nameservers of a domain within that account. This way, I do not need to visit all my managed databases rules and firewall rules when an IP address changes of one of my locations. For example: Dynamic Home IP, of which I update an A record in DO Domain automatically via the DO Api when it changes Failover WAN ip which is a mobile connection an can change IP any time, locking me out of my databases/firewalls. All I need to do is change the IP in the DNS of DO and I should be fine.