Imo it’s quite nice to not have a public domain like cloud.example.com which is much longer and all the gold ones are taken anyway.
Putting these local ones in my dns server is no issue, but getting https to work seems like a pain. I set up caddy to use its own certificate authority, but even when installing the root certificate to windows, many programs still don’t truth it and most of them don’t show a useful error message. Additionally getting them to trust the certificate is fiddely and then try to explain that to your mom so she can use my cloud.
All this makes me thing about switching back to public subdomains so I can get lets encrypt certificates


I use .internal, setup a self-hosted certificate authority providing ACME to servers. The certificate is set to only be valid on .internal domains and not the entire internet and enrolled on my phone and computers.
I’ve never liked this approach - having to enroll certs on every machine always seemed tedious and it’s why I just “dealt with” having HTTPS errors internally for years.
Honest question, why not set up a reverse proxy that uses Let’s Encrypt? It will handle internal domains if configured appropriately, and then you only have to configure at the proxy and DNS level.
You only have to do it once per machine and I use NixOS a lot so its easy to just add to a module imported by every system. On other Linux systems it’s just putting the pem file somewhere in /etc/ and running a command to reload it. Android cell phones were pretty easy but I forget the exact details.
I have multiple of those for public services. Because I don’t want to expose every service to the internet for HTTP-01 and can’t use DNS-01 due to how my nameservers are set up, this makes sense. Other advantages are not needing to distribute DNS update keys to every single server for security reasons and having shorter domains.