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.
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.I still think they shouldn’t be used - they’re still unregistered
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!)
I have my own domain with a cert so it is (service).reannlegge.ca in caddy, I don’t really let many of my things out onto the web without the VPN but it is nice having the https and not having to see the this site may not be secure for almost everything I do.
You don’t have to own a domain. As long as you can satisfy a challenge, such as by publishing a web page under the domain for the HTTP-01 challenge, you can still get certs.
Many years ago I settled on a real domain using reverse proxies / dns overrides so that local and remote work the same. Workflow has been working for well over a decade.
This. Also, if you don’t want to allow remote access, you can still use a real domain. It’s possible to use public DNS only for the ACME challenge, and local DNS for everything else.
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.
Nah. Proper domain or no domain. It doesn’t take much to have your home network be, for example, home.hdhdhdgsg.cum
The need for “proper domains”, where “proper” nowadays seems to mean “Trump-approved”, is an important risk, because then the identity of your homelab depends on the DNS and SSL cartel. It’s one of the reasons I distrust the Gemini protocol and consider it a raw downgrade from Gopher (and from HTML, for that matter).
If
home.arpais the way to go local, then it’s the way to go local.The certificate problem that you are running into is the same one I ran into and why I got a domain.
Now I have Traefik get a wildcard cert from LE and no more issues.
I don’t have anything publicly accessible so my public DNS record points to an IP on my lan.
Browser autocompletes the longer domains anyway, so not really a big deal. I use xyz.internal.mydomain.com as my naming scheme, and the easy certificates are definitely worth it.
Using single-label domain names isn’t browser autocompletion, it’s RFC 1034 standard domain resolution behavior based on your search list.
I mostly use .lan domains without TLS on my local network, but I recently got a Roborock vacuum and wanted to use Roborock Local Server, but the vacuum would only connect if my local server had TLS, so I bought a domain.




