Network

We would like to suggest a feature that allows assigning multiple reserved IP addresses to a single Droplet. Currently, the DigitalOcean platform permits only one reserved IP per Droplet via the control panel. Enabling support for multiple reserved IPs per Droplet would be highly useful in various production use cases, such as advanced routing, service isolation, and legacy system support. We believe this capability would add flexibility for teams managing complex infrastructure setups on DigitalOcean.

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.

There should be a list of IP addresses used by Uptime Monitor to whitelist in firewall settings.

Add bgp session with default gateway received. For Beeing able to use your own AS and IP network. Possible with private vlan.

Current situation: If I enter my root domain into the "hostname" field I'm only allowed to create entries such as A, AAAAA, MX etc. but not CNAME. Wanted situation: I can create a CNAME entry with my root domain and this will be flattened automatically, like Cloudflare does ( https://support.cloudflare.com/hc/en-us/articles/200169056-CNAME-Flattening-RFC-compliant-support-for-CNAME-at-the-root )

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 ?!

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.

I use the firewalls to block SSH from all but our employee IPs. However, those IPs change weekly, and I end up having to maintain a map and it's really confusing. I'd like to have a way to name them so I can easily update them. Different ways I've done this with traditional firewalls: • Create one SSH rule per person and name the rule • Create a named machine with an IP for each person, and add all those machines to the SSH rule Please please please let me know if this is something you can accommodate in the future.

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