Replies

• on 🌐 : @techlifeweb how about .local?
• on 🌐 : @techlifeweb FWIW I use `internal.strugee.net` as my LAN domain... and I have run into problems because strugee.net is on the HSTS preload list (https://hstspreload.org/), and I don't want to maintain a globally valid TLS certificate on any of my networking equipment that's only accessible from my LAN. YMMV. HSTS Preload List Submission
• on 🐘 : @GuillaumeRossolini I've read specifically not to use that. Example: https://www.ctrl.blog/entry/homenet-domain-name/ What domain name to use for your home network
• on 🌐 : @techlifeweb that is so weird, I thought this was the thing to use? Probably we need to wait a few decades until drivers and firmwares are onto this
• on 🐘 : @GuillaumeRossolini I think you're right and it was the thing to use but then some standards changed. Apparently. internal is for businesses and .home.arpa is for home networks. I don't really know enough to know how big of an issue it would be to leave it as .local (probably close to zero) but I decided against it.
• on 🌐 : @techlifeweb I don’t enjoy too much the inherent adherence to the US by using .arpa It may have been retrofitted, but who knows
• on 🐘 : @techlifeweb Thanks for sharing, I was not aware of this standard! I've been doing the .something.realdomain.example.com approach for some years now and I can't really come up with any advantages of the .home.arpa one, unless you really don't have _any_ domains.
• on 🐘 : @glyph You're probably right and I have a domain I should just use but I thought I'd see, for now, how this goes.

Likes

• 

Reposts