Really really well done DO!
It truncates both the record contents and the domain name, which means that if you've got a bunch of long domains with TXT records, telling them apart means copying the contents into a text editor to see the truncated text.
e.g
somekey._dkim.subdomaina.domain.com k=rsa; t=s; p=MIGfAAAA
somekey._dkim.subdomainb.domain.com k=rsa; t=s; p=MIGfBBBB
somekey._dkim.subdomainc.domain.com k=rsa; t=s; p=MIGfAAAA
getting truncated down to somekey._dkim.subdo... k=rsa; t=s; p=MI...
somekey._dkim.subdo... k=rsa; t=s; p=MI...
somekey._dkim.subdo... k=rsa; t=s; p=MI...
Compared to AWS, which is visually unappealing, but I can actually see my DNS records....But I agree, that with something that coins itself "the developer cloud" it should provide critical information first. It is ok to kill some whitespace or put some monospaced fonts in there. You aren't trying to sell me an iPhone, I am trying to manage a server.
Route53 on AWS is what I have been using for domain management and I like it because it doesn't mess around with cute UIs. It is strictly function. Instead of form fields for each TTL line and host line like other sites do, you just get a big multi-line text box and you use spaces and line breaks (gasp) to create your dns listings.
https://www.digitalocean.com/docs/networking/ipv6/
Yes, you read that right, they assign a /124 if you enable IPv6. There is no provision for getting anything larger. All configuration is totally static as well. It's really incredible how botched the setup is, and it has been like this for years.
If you're wondering if you're sharing the same /64 with an entire datacenter worth of droplets, the answer is of course.
I haven't contacted them about it but that makes sense sadly. So they're getting a /64 from their upstream and just sharing that out to everyone. This isn't IPv4, they need to make this right.
Vultr, OTOH, gives each HOST a /64. I've been doing most of my work on Vultr right now so I can use more than 16 IPs on a single host. I was/am hoping that providers would standardize somewhere in the middle: Every customer account in each datacenter gets a /64. I wouldn't mind all of my hosts having their own /64 to subdivide.
It's not like it is hard to get IPv6 address space either. All they have to do is ask. A VPS provider like DO can get a /32 easy peasy.
(And a /48 from APNIC???)
(Edit: And a /36, /40 and /48 from APNIC?)
Edit: I'm wrong, see below.
> You cannot assign a Floating IP to a Droplet created from a custom image.
Edit: I wanted to double-check because this would make my life so much easier, but no, I still can't use Floating IP with Custom Images. I imported a FlatcarLinux image from a URL and created a droplet; once the droplet launched, I still see this:
> Floating IP: Disabled
> Public IPv6 Address: Not available with custom images.
Speculating and recalling old memories here, but: floating IP is implemented as an additional IP on an existing interface. DHCP can't assign multiple IPs for the same MAC. So there's got to be some DigitalOcean magic in the base images to figure out that a floating IP is assigned and configure the interface for it. You might be able to replicate this yourself, they just don't want to be responsible for support.
Perhaps over time they will grow a more complex network fabric that will enable floating IPs to be their own DHCP-enabled interfaces straight on VMs, instead of the "dumb" forwarding rules they appear to be today. But also perhaps the lack of such things is why DigitalOcean is cheaper than Amazon.
(3) was the cause of numerous production incidents for us. We had to contact support to have it scaled up, and sometimes they'd take up to 3 working days to get back to us. Happily paid more for AWS to get better support, and stability.
https://wakatime.com/blog/46-latency-of-digitalocean-spaces-...
Not being able to give just DNS access to a script for updating LE/ACME DNS challenges means it'd be a non-starter at work.
This is the case for literally every managed database service that I'm aware of.
You pay a premium for the managed aspect.
That’s been my experience, at least.
BUT:
1. Their web UI stability is terrible (constantly hangs and errors out)
2. Their hosted DB IOPS aren't competitive with other PaaS providers. There's also no way to scale DB size dynamically without upgrading to a new price tier which is overkill.
3. Their Kubernetes Control Plane scaling is obfuscated. I had to contact support to realize that the control plane nodes are somehow tied to the size of your node pool when you create the cluster? That's not documented anywhere and was the cause of many control plane timeouts.
4. No ALIAS dns record, no way to serve Spaces from an apex domain. (I know this is a vendor specific implementation but it's table stakes imo)
Again, I'm a (mostly) happy DO customer and wish them the best but if they really want to be seen on the same level as AWS or GCP in terms of some parity, they need to include some of these QoL features.