On Fri 02 Aug 2024 at 14:37:08 (+1000), George at Clug wrote: > > > What is best practice for a local LAN prefix? (I have never found > > > conclusive instruction). > > > > home.arpa > > see https://www.rfc-editor.org/rfc/rfc8375.html > > A fairly straight forward statement in this RFC, just not sure if I could get > used to using .arpa as a suffix. But seems like a great choice?
If you're heavily into DNS, then you've probably used the .arpa TLD already, as in ….in-addr.arpa, which maps IPv4 addresses to domain names, and ….ip6.arpa for IPv6. It's now a backronym standing for Address and Routing Parameter Area, to decouple it from its original coining. > > > It is my belief that .local is a MS idea originating from the > > > configuration of their servers. Is this correct? > > > > again, quoting from the .local wikipedia article > > Microsoft TechNet article 708159[7] suggested .local ... > > but later recommended against it > > https://en.wikipedia.org/wiki/.local > If you have *Macintosh client computers* that are running the Macintosh OS X > version 10.3 operating system or later, ... it is recommended that you do not > use the .local label for the full DNS name of your internal domain. That TechNet article was written in 2008. I think .local was being used by Apple in the previous decade (see RFC). The cynic in me wonders whether this article is an attempt to lock in MS customers. Look at the paragraph after the one you quoted: "• After you install Windows Small Business Server 2003, you cannot change the settings specified in Full DNS name for internal domain or NetBIOS domain name. These settings are used to configure server applications during Setup. If you want to change these names, you must reinstall Windows Small Business Server 2003." Either they're trying to make things difficult should you go out and buy any Apple kit, or they're relying on people not to read any of the warnings, and go with their default. Cheers, David.
