Earlier quoted context omitted.
Editing the hosts file isn't a solution for internal use in organizations. If it's just you, editing your hosts file, switch to .local or whatever. There was always a chance when using a "local" domain (which isn't actually some sort of standard) that such a TLD could be created in the future. If it's for an organization, create the root cert, and have that be one of the steps users need to take in order to access th…
.local is reserved for multicast DNS/zeroconf, by the standard. You literally can’t use it on macos because it will always try to look it up in with mDNS first, and only fall back on /etc/hosts once that fails. If you use .local for fake DNS for a dev setup, you’ll probably notice lookups are slow; that’s why. (This is why I’ve always used .dev actually, although this may make me switch to .fuckgoogle or something in…
Why not .fuckapple? Really, .local is defined for local address, if Apple is using it in a fucked up way this is an Apple problem.
.dev was never destined for local address, it was just because it wasn't registered in ICANN yet.