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 ;)
Domain Registration / Sell Domain Names
Have one solution for everything.. Selling domain's which automatically point to NS1.DIGITALOCEAN.COM , NS2.DIGITALOCEAN.COM , NS3.DIGITALOCEAN.COM . I would love to just have one service for everything web.
Allow GRE packets through the firewall
Currently the DO firewall filters IP Protocol 47 (GRE) packets, which interferes with pptp vpn links. If GRE packets were added to the list, along with ICMP, IPv4 and IPv6, this would allow the use of PPTP VPNs (see e.g. https://www.digitalocean.com/community/tutorials/how-to-setup-your-own-vpn-with-pptp ) and other VPNs that utilize GRE packets, such as IPSec
Global Load Balancer
It would be great to have global load balancer so we can do direct traffic to nearest region where we have deployed our http/https service.