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 have a public domain, and use a subdomain for my homelab -
.lab.myfqdn.com. I do public DNS ACME challenges for a wildcard*.lab.myfqdn.com.It’s a double bonus because I don’t have SSL cert records leaked to the internet, and I can also browse internal services on my devices and family devices without having to do weird stuff with SSL cert trusts.