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
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.
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 use a real domain and then reverse proxy via NPM
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.
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.proposals
https://datatracker.ietf.org/doc/html/rfc6762#appendix-G
Document type
RFC - Proposed Standard
February 2013
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!)
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.
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.
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.
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.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters CA (SSL) Certificate Authority DNS Domain Name Service/System ESPA EELV Secondary Payload Adapter standard for attaching to a second stage ISP Internet Service Provider TLS Transport Layer Security, supersedes SSL VPN Virtual Private Network
[Thread #172 for this comm, first seen 20th Nov 2026, 08:00] [FAQ] [Full list] [Contact] [Source code]
x.home.arpa was made for this situation. I’ve been able to use caddy’s certificate with no issues.
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.
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.
Nah. Proper domain or no domain.
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.
Having access to port 80 on the IP associated with a domain but not to the DNS raises some interesting questions. 🙂
Unless it’s purely a matter of personal preference but I for one don’t see why you’d want to do HTTP-01 (as a self-hoster) unless forced. It can’t do wildcards, for one thing. And you need an
Arecord pointing to your public IP, and if your public IP is dynamic you need to do DDNS, and open port 80 and so on. That’s a lot of moving pieces that make automation hard.Also, if you’re doing DDNS there’s a chance the DNS has some sort of API that might also work for certbot. Granted it’s not a given, I’ve seen registrars that offer a DDNS link but not something you’d call an actual DNS API.
But anyway finding a decent DNS provider with a certbot-friendly API is not that hard.
The main use case is someone using a free subdomain. It’s not that uncommon.
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 dunno if we are referring to the same thing, I mean the browser feature where URLs you’ve visited previously will be auto-suggested by the browser as you type. But I dont fully understand the rfc feature your referring to, so maybe we are thinking of the same thing?
Either way, the browser makes it easy to revisit URLs without typing the full address.
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.







