It's easier to remember the IPs of good DNSes, too.
It's easier to remember the IPs of good DNSes, too.
Today in our newest take on "older technology is better": why NAT rules!
You're viewing a single thread.
Slightly related to the issue of remembering addresses, I think the main issue is with the fact that local nameservers are pretty much non-existent if you're not running OpenWrt or OpnSense. Which is shameful because the local nameserver is an amazing quality of life tool.
Also the fact that officially there are no local TLDs except for ".arpa" while browsers won't resolve one word domains without adding http://
And don't get me started on TLS certificates in local networks... (although dns01 saves the day)
I don't get why '.local' isn't a top level domain for LAN hosts.
I've taken to using
.here(or.aqui, "here" in Español, much harder to match outside) as alternatives until something better comes up.Ideally I'd use
.aquí, correctly with the diacritic, but DNS doesn't seem to support even the basics of Unicode in 2024.Well, there is Punycode, which, if I understand correctly, is a layer before DNS, which translates a Unicode string into a DNS-compatible ASCII string.
I don't actually recommend using that, though. Every so often, the ugly ASCII string shows up in places, because Punycode translation isn't implemented there. Certainly increases administration complexity.
Yeah I've heard about punycode. Personally, I'm well against it because it puts down non-MURRICAN English domain names as second-class citizens on the internet. If I have a website about Copiapó, a perfectly legal town, there's no good reason why the domain name should not be
copiapó.clrather thancopiap-xcwhngoingohi4oleleiyho42yt4ptg4ht4.cl, making it look "suspect" and "malware-y".There were quite some complains back in the time about Firefox choosing not to "flag" internationalized names as potentially dangerous, and pretty much all those complaints that I know of likely came from English speakers who simply can't understand other countries in the world even can have different alphabets.
I mean, there is some legitimate concerns. For example, in theory, someone could register a domain "αpple.com" and use that to send phishing mails. That "α" is an alpha. The more alphabets and letter variants you allow, the more lookalikes there will be.
But yeah, in practice, domain registrars check that you're not registering such a lookalike domain and then that's not really a problem, as far as I'm aware.
.localis already used by mDNSAh, that makes sense. I just knew it was unavailable. Apparently
.lanis fine to use, I think I'll try that next time.
And don’t get me started on TLS certificates in local networks…
I hate this and the fact that modern platforms seem to require TLS even if you're serving localhost, so much.