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 )

Recently UDP port support was added to Load Balancers (see also e.g. https://docs.digitalocean.com/products/kubernetes/how-to/configure-load-balancers/#protocol ). This allows for various useful applications, in particular support for HTTP/3. However, this protocol does not allow using PROXY Protocol as of yet (as has been confirmed by my contact with DO support). This means that it is not possible to use the client IP for any purpose when using both HTTP/3 and TLS Passthrough on a Load Balancer. This idea suggests implementing the PROXY Protocol for UDP traffic as well, so that the original client IP is exposed to the service behind the Load Balancer.

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.

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.

It would be great if we could communicate across multiple VPC networks in the same datacenter region. This would allow to create a VPC for front-end web servers and a separate VPC for back-end servers and utilizing cloud firewalls to restrict what ports can traverse the two VPCs.

More than one ip for a VM would be great. A small subnet maybe ..

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.

The aibility to point many domains on a single loadbalancer with their ssl certificate, also wildcard certificate, for now I'm using cloudflare flexible ssl with proxied feature to link many domains

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.

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.