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


Can I recommend that you move that record to the local DNS? Assuming your router’s firmware has this feature and you can access it.
Private IPs in public DNS are associated with certain types of attacks and they get filtered by some DNS servers, routers or ISPs so you may run into intermittent “unexplained” hiccups.
Secondly, if your internet ever goes down in the middle of the night and the records expire from the local DNS cache by morning, you won’t be able to resolve anything on your LAN anymore. Which is a pity because it’s unnecessary, your local setup can work fine independent of the internet connection.
Last but not least, there are actors out there that use a variety of methods to gather information about the infrastructure behind each domain and the least such information you put out there, the better.
Run your domain through DNS Robot to get an idea.
I have adguard home to intercept the requests. Private IPs in public DNS is a non issue. We did it quite a bit at the ISP I worked at.
Were you doing split DNS? The average registrar DNS or end-user DNS provider is not typically split-capable.