Network

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.

Very simple. Ipv4 AND ipv6 records with floating ip's

It would be helpful to be able to block traffic from entire countries using the cloud firewall. 90% of the malicious traffic we get is from China, Russia, Brazil, etc. Being able to block at the firewall level would greatly reduce this malicious traffic.

GEO DNS + Multiple droplets.. is more than AWESOME setup..!! I'd love to see this service soon in DO, where you can create several droplets in several data centers and point your DNS zones toward these droplet. Visitors from NY for example get served by NY Droplet(s), Visitors from AMS get served by AMS Droplet(s). This way, you can build your own CDN within few moments, and get your websites performance-extra-charged. Your Votes, comments ?!

Some cloud providers (e.g. AWS with ACM) offers CNAME-based SSL, which are SSL certificates issued by the provider, validate via a CNAME record. Basically, we can request a certificate and validate the domain ownership via CNAMEs, and the cloud provider generates and renews the certificate automatically. We can, then, use the certificate in a Load Balancer. Currently, in DigitalOcean (DO), we can only have auto-generated certificates if we point our nameservers to DO's. This feature is particularly interesting when running a multi-tenant application that allows customers to use their own domains. In this case, we can't ask customers to point their nameservers, but asking them to provide some CNAMEs is a good solution. We are particularly interested in the multi-tenant use case. I have attached some pictures of the process in AWS.

Currently, DigitalOcean blocks all SMTP traffic on IPv6 droplets. This doesn't make much sense, since SMTP traffic can be sent over IPv4. DigitalOcean should at least have the option to enable SMTP traffic over IPv6 for certain customers (same as with IPv4).

I'm finding that my legitimate site is appearing on blocklists (spamhaus and proofpoint), presumably because my 'neighours' in the netblock are behaving badly. Can you please make it more difficult for spammers to operate outgoing mail servers? One major obstacle could be requiring a substantial deposit ($100USD/EUR) to be made to their account, which would be forfeited if they are credibly accused of spamming.

As you guys are testing IPv6 in the Singapore region, I highly recommend you give users a /64 each when IPv6 rolls out. This is proper practice, and gives users more flexibility in terms of address selection.

Please allow droplets to send mail via IPv6.

Remove requirement for public IP. Not all droplets need to have a dedicated public IP address. Instead, allow us to have 1 gateway per VPC that the droplets can reach the Internet from.