I just bought an actual domain and use that π
As an added bonus, letsencrypt works with no effort.
this post was submitted on 10 Jul 2023
40 points (97.6% liked)
Selfhosted
38768 readers
178 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (donβt cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Same here. Well worth it for $10 a year
same. saved my ass already a few times when doing some reverseengineering voodoo. being able to set a valid https cert makes it easier to redirect apps than to bypass forced HTTPS. had to pretend to be a update server for something once and patching the URL was enough via getting a cert quickly (using DNS-01 challenge, no exposed ports ever)
You shouldn't use .local for your manually defined local domain names if you plan to ever use mdns/avahi/bonjour/zeroconf.
And .box has been registered as a generic TLD now, so you could run into external .box domains.
Hopefully AVM gets to register fritz.box then, because they've been setting up their customers with that as their internal domain for ages...
I actually use .lan for an internal domain but I guess I could use a real domain with the DNS-01 challenge and have real internal certificates. I had not thought about that until just now.
According to IETF, you should only use .intranet, .internal, .private, .corp, .home or .lan for your private network ( RFC 6762 Appendix G ). Using other TLDs might cause issues in the future, especially since new gTLDs seems to show up every few months or so, which can collide with the TLD you use for your local network.
The one reserved for residential usage is home.arpa.
Interesting, so this is the latest recommendation? Which is probably why I haven't seen it in the wild yet, at least in my circles.
Which means they probably going to ~~cash out~~ release gTLDs for .intranet, .internal, .private, .corp, .home and .lan soon...
A problem with the .lan TLD (maybe others from this list) is that web browsers do not consider it a TLD when you type it in the address bar, and only show you the option to search for that term in your default search engine. You have to explicitly type https:// before it, to have the option to visit the URL.
E.g type example.com in the address bar -> pressing Enter triggers going to https://example.com. Type example.lan -> pressing Enter triggers a search for example.lan using your default search engine.
Little known trick--or perhaps everyone knows it and is quietly laughing behind my back--with Chromium browsers and Firefox (and maybe Safari, I'm not sure), you can add a slash to the end of an address and it will bypass the search.
So, for example, my router on the LAN goes by the hostname "pfsense". I can then type pfsense.lan/ into my address bar and it will bring me to the web UI, no HTTP/s needed.
You can throw a / after to force it to recognize as a URL too.
@redcalcium
Really? Not .local? Why is it the default on so much?
@zephyr
A long time ago Microsoft and some teaching sources used .local in example documentation for local domains and it stuck. Like contoso.com was Microsoft's example company. I was taught to use .local decades ago and it took a very long time to unlearn it.
I can vouch for the fact that .local stopped working suddenly in most browsers a year or two ago, I was forced to migrate to .internal
There actually is a correct awnser: home.arpa
See https://www.ctrl.blog/entry/homenet-domain-name.html
i use my external zone name but have an internal view of the zone inside my lan so records point to local ips.
Split Horizon DNS is the most seamless user experience.
I use subdomains, i., w. for wifi, few others for vms and containers.
With wireguard everything just works, and wireguard overhead over wireless is negligible even on wifi6.
I agree on WireGuard. It's clearly the winner in terms of speed for point to point VPN.
Exactly the same. I'd like to add that my devices still get a .lan TLD from the router.
Same here. I have several domains, one is used for servers and email, 2nd for websites, 3rd for messing around (test setups) and a 4th is almost unused now, but with the demise of twitter and reddit I'm thinking of using that one for the fediverse (it's my username in national tld).
BTW internal and external dns run on different systems and all private zones are dnssec signed. (Loved the challenge on setting that up correctly)
Same, I achieve this with Adguard DNS rewrite.
*.internal.domain.name since ssl certs are easier to get when youβre using an owned domain name.
Thereβs a draft rfc that defines β.home.arpaβ as an internal. It looks stupid and totally misses the point, but works.
Yes, it does look stupid. I'd rather .lan just be reserved for private networks.
I use a subdomain of a domain name I own.
I bought a .com for like $10 CAD from Cloudflare that uses a URL not linked to me.
Maybe overly paranoid, but it also makes it easy to get SSL certificates for my lab.
For local DNS home.arpa is I think what we're 'supposed' to use, but I use .lan
Only use another domain name if you actually have it registered, like myname.net or something. As a bonus you can then get a wildcard letsencrypt SSL cert for easy HTTPS.
Why should you only use ones you own, even if it's just local network?
Because of interference with existing domains. Say you set a computer on your network to mypc.google.com, that won't work because the DNS server will lookup google.com as an external domain.
I tend to use .local
That will work fine so long as you don't need services like Avahi and mDNS.
server.home for my part
I use .lan for everything the router can resolve names for, and .local for Avahi mDNS π
I use either .home or an actual domain that I own (makes it easy for https certs and not having to go out of the network and back in)
I use home.arpa for all my LAN hosts.
fritz.box for the machines themselves because Fritz!BOX (although handed out by Pi-Hole),but .lan for anything going over the local proxy towards the same machine for TLS.
Some machines use my custom domain name instead of .lan, if they need to be accessible from outside. So these last ones go directly over the local proxy internally, but automatically over CloudFlare Tunnel and Authentik when not at home. The proxy being Caddy.
.home.lan for me.
my server is just server
.lan for everything.
I also use .lan I used to use .local for years until I started to have conflict issues with .local resolution on Android when they started using mdns
I didn't care about any of this (my off the shelf Router used .local) and then I started selfhosting more and using pFsense as a router OS. It defaulted to using home.arpa, which was so objectionable that I spent time looking into RFC 6762 and promptly reverted to .lan forever.
The official choices were: .intranet, .internal, .home, .lan, .corp, and .private. LAN was the shortest and most applicable. Choice made.
view more: next βΊ