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


As far as I’m aware, the only “local” domains are the ones reserved in the RFC, e.g. home.arpa
Everything else is just a public domain you don’t own, or not a domain. Using a domain that you don’t have authority over carries risks, even if you think you’ve kept everything local. Just use a real domain that belongs to you.
.internal was registered for private use by ICANN in 2024
(If you’re going to use something other than .home.arpa, it should be that one.)
Nice one, wasn’t aware of that. Internal sounds like a nice option in that context, especially outside of home networks
Thanks for that detail!
I thought it was still “de facto” rather than “de jure” by this point.
100% this.
home.arpais the proper way to do this.Unless you have a domain you own, which I do, but still use
home.arpaanyway.What about https://en.wikipedia.org/wiki/List_of_internet_top-level_domains#Internet_Engineering_Task_Force_proposals_for_local_TLDs ?
https://datatracker.ietf.org/doc/html/rfc6762#appendix-G
https://stackoverflow.com/a/778275
I still think they shouldn’t be used - they’re still unregistered (edit except for .internal)
https://datatracker.ietf.org/doc/html/rfc6762#appendix-G
mDNS is weird though, device implementations can often deviate so far from the RFC that you need to rely on the ones there. (I’m really bad with mDNS, someone else feel free to prove me wrong!)