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 them both at home and in work. For https, just go with self signed certs.
.lan is being proposed as a new TLD so I wouldn’t start using that for a new system. .internal is the safe option. https://news.ycombinator.com/item?id=50007353
In my setup I just use a public domain to make TLS easier.
I use .lan for most local stuff, since it’s local only I don’t bother with HTTPS at all.
Anything that needs it like Vaultwarden just goes on a real domain so a letsencrypt wildcard cert works.
I use *.local.(mydomain).xyz
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.
.lan is super common and won’t have any issues.
RFC 8375 is such a joke
Using lan is the standard even if the standards bodies refuse to recognize it. Even openwrt uses it and they typically adhere to the RFC
.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.Just use .lan
It is way simpler and has been in use long before .home.arpa
Use the RFC defined special use domain https://www.iana.org/assignments/special-use-domain-names
Why though?
It was pushed as a standard after .lan was in use
For the same reason you use RFC provided private IPv4 ranges.
RFC 1918 reserves three IPv4 private address ranges: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. These ranges are not publicly routable on the global Internet.
Because there is a standard.
Also, there is nothing stopping
lan.getting registered as a TLD.Except that isn’t really a fair comparison. Private ranges aren’t any more complicated than public ranges so it doesn’t impact me when using IPv4 private IPs.
.home.arpa is one of the most “designed by committee” domains I have heard in my life. It is way longer than .lan and defeats the point of local domains to begin with. I might as well use a public domain instead. .lan was around long before the standard and will be around long after
If .lan becomes a TLD (it won’t) I can always go though and change it to something like lan1 or .mylan both of which would be shorter and easier to type
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!)
proposals
https://datatracker.ietf.org/doc/html/rfc6762#appendix-G
Document type
RFC - Proposed Standard
February 2013
like cloud.example.com which is much longer and all the gold ones are taken anyway.
You can try getting a shorter domain from a ccTLD. I’ve probed my country’s whois for 1-3 digit domains once on a whim and stumbled across one that was free.
How did you do that search? I was only able to find cheat five character domains
Just a shell script running
whoisin a loop and looking at the output, with random sleep intervals in-between. Left it running overnight, 1100 domains is not a lot (I also checked the versions with with zero padding).I was only able to find cheat five character domains
Probably depends a lot on the country TLD.
I use a real domain and then reverse proxy via NPM
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.
You don’t even need public DNS at all. My public domain points all records to 192.168.1.1, and Caddy registers certs without any issues.
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.
That’s the most common sense approach, so you don’t run into situations where your Internet is down and you’re trying to resolve a LAN IP through an unreachable public server. Records may or may not be cached anymore on the local when the connection goes down.
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.
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.
Why use Traefik? You could just put a reverse proxy on each device and then automate it all with a simple script
??? Traefik is a reverse proxy
How many instances are you running. Having a single point of failure seems risky to me
Its a home lab spof are totally fine. I do need better uptime then Github but not 3 or 4 9s.
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.
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.
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.
Honest question, why not set up a reverse proxy that uses Let’s Encrypt?
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.
All of my services are currently local only so I just run http on all of them. I do still like being able to use a hostname instead of memorizing port numbers for everything so I do use
*.home.lan.Eventually I will be exposing some services but right now I am behind cgnat and don’t have a decent router to support modern ipv6 yet.
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.
Using self signed as a route that it’s not going to work after you factor in service specific apps that refuse your self signed certs, phones where installing those certs is a pain, and the overall WAF where installing those certs might just put off family users.
Add in the mix the new Android 17 fucking “feature” where apps need special permissions to access the local network … (Yeah, Dav5x, home assistant, even Firefox stopped working on my on Android until I figured this out after upgrading to 17). I will write a post on this topic later on today.
Self signed also makes it easy for someone to compromise https on your network
If you need to use a self sign certificate make sure to add name restrictions in the root so that it can’t be used for public domains
x.home.arpa was made for this situation. I’ve been able to use caddy’s certificate with no issues.
Nah. Proper domain or no domain.












