Today in our newest take on “older technology is better”: why NAT rules!
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’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.