Network

This is field allows clients to discover protocol availability such as HTTP/3. https://gcore.com/docs/dns/dns-records/what-is-an-https-record-and-how-is-it-configured

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 requires manually operation after you associate Droplets as NLB backend, see https://docs.digitalocean.com/products/networking/load-balancers/how-to/configure-droplets-for-nlb/ if customer forget to do so, traffic to NLB never success. and when they added new Droplets, there will be silent packets loss with these new Droplets as they did not have correct route table.

currently only API & CLI method supported to configure Load Balancer firewall, it's not user friendly especially API & CLI update Load Balancer with PUT, not PATCH. as you have to provide the full parameters of the Load Balancer otherwise the specific parameter will reset to default, it's very easy to make production disruptions. CLI method not support to use json file, something like API curl --data or MySQL config-json, it makes CLI very hard to use. requirements: support update Load Balancer firewall with UI use PATCH but not PUT method with API & CLI when updating Load Balancer, just something like when you update MySQL configuration, see https://docs.digitalocean.com/reference/doctl/reference/databases/configuration/update/ support use local json file with doctl

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.

IPv6 should be on by default for all new droplets, it's 2023

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.

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.

It would be great to be able to put app platform instances into VPCs.

not only droplets but also load balancers should be put behind the firewalls