On 3 Aug 2024 22:22 +0100, from mick.cr...@gmail.com (mick.crane): > I was going to change everything yet again to home.arpa but now it might be > .internal?
To use .home.arpa is absolutely fine if you don't need (or want) globally unique names. It has been properly assigned specifically for "non-unique use in residential home networks". (RFC 8375.) .internal is _in the process of_ being standardized for "private applications". It isn't quite there yet, but it _has_ been reserved for that purpose in the global root DNS zone so unless the ICANN Board reneges on that decision no one is going to buy themselves a gTLD of .internal either now or in the future. The downsides of using .home.arpa over .internal (as proposed) are basically only that (a) it's two labels instead of one, which some people care about; and (b) it _looks_ weird in a corporate or other organizational context to have a word referencing residential use in hostnames. I'm pretty sure a bare .home has never been recommended other than as a default for HNCP (which was since changed), and in any case people coming up with so many different variants on their own shows the value of standardizing on something especially in the current world where acquiring a gTLD is _far_ easier than it was a few decades ago. Just look at the mess it must have created with what people intended as internal names when Google not only acquired .dev, but also made it a HSTS-preloaded TLD. (And no, effectively saying "we don't recommend it, but if you must, here are some that people use" does not constitute a recommendation.) -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
