There are many DNS names options. Which one do you use?
I just bought an actual domain and use that 😅
As an added bonus, letsencrypt works with no effort.
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
.boxhas been registered as a generic TLD now, so you could run into external .box domains.Hopefully AVM gets to register
fritz.boxthen, because they’ve been setting up their customers with that as their internal domain for ages…
*.internal.domain.namesince ssl certs are easier to get when you’re using an owned domain name.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.
There’s a draft rfc that defines “.home.arpa” as an internal. It looks stupid and totally misses the point, but works.
I use a subdomain of a domain name I own.
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.arpafor all my LAN hosts..home.lan for me.
server.home for my part
Idk is that wrong but I made up server name tride so .tride is my local domain
I use .lan for everything the router can resolve names for, and .local for Avahi mDNS 😈
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.
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
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.
