In order to protect CoAP/DTLS Connection ID traffic state of the art, please add some simple rules to filter DTLS 1.2 Connection ID records. That could be easily done by filter on the first 3 bytes. DTLS 1.2 header first 3 bytes "14 fe fd" (CCS, 1.2) "15 fe fd" (Alert, 1.2) "16 fe fd" (Handshake, 1.2) "17 fe fd" (Application Data, 1.2) "19 fe fd" (tls_cid, 1.2) And DTLS 1.0 header for HelloVerifyRequest "16 fe ff" (Handshake, 1.0) See https://github.com/eclipse/californium/wiki/DTLS-1.2-based-firewall

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.

I have rules on the firewall that only allow access to ports from my home IP. My home IP is not static and can change. I do though have a DDNS service for my home IP that gets updated on IP change. It would be great if the firewall can use the DDNS address as the source.

I want to Firewall ssh (port 22) but still want Digital Ocean web site Console and Droplet Console to work for the droplet. I added the Digital Ocean IP addresses I found being used (162.243.188.66, 162.243.190.66, 198.211.111.194), but would like this to always work. So, will you make an option for having a "Firewall exception for Droplet Console ssh" to your firewalls to either allow or block Digital Ocean Droplet Console ssh access - that would be very nice! Thanks, Kevin Crothers

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 )

DNS Record List should have a filtration to view based on DNS Records Types (i.e. A, TXT, etc). As of right now, it just shows all records in one page thus making a lot of confusion when having a lot of records.

Edit DNS zone file directly or/and implement import/export tool to make migration easier

https://tools.ietf.org/html/rfc4255

Add ability to change private IP of a droplet in a VPC.