What hostname do you use for server? home.box or home.local?

zephyr@lemmy.world to Selfhosted@lemmy.world – 35 points –

There are many DNS names options. Which one do you use?

70

I just bought an actual domain and use that πŸ˜…

As an added bonus, letsencrypt works with no effort.

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)

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.

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.

@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

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.

*.internal.domain.name since ssl certs are easier to get when you’re using an owned domain name.

i use my external zone name but have an internal view of the zone inside my lan so records point to local ips.

I use subdomains, i.<external domain>, w.<ext> for wifi, few others for vms and containers.

With wireguard everything just works, and wireguard overhead over wireless is negligible even on wifi6.

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)

3 more...

I use a subdomain of a domain name I own.

There’s a draft rfc that defines β€œ.home.arpa” as an internal. It looks stupid and totally misses the point, but works.

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 use home.arpa for all my LAN hosts.

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 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.

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.

nothing as home does work (meaning plain hostname) works by default on openwrt dns

While this works for most things, you will run into issues with certain software which automatically assume that no TLD means the provided address is incorrect.

Usually adding a slash at the end works if the protocol is http based

I use .lan for everything the router can resolve names for, and .local for Avahi mDNS 😈

Idk is that wrong but I made up server name tride so .tride is my local domain

hostname.vlan.local.lan

local.lan is the only fixed part of my fqdn's

.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.

I use different ones. Got an legit dpmain which I also use locally (with ssl certificates) and in my local network my server listens to SERVI. Just SERVI.