On Tue, 2007-11-20 at 14:59 -0700, David L. Willson wrote: > About this .local domain: I know there's an RFC that defines it for use > with multicast, but I was not aware that "the Microsoft one is the one > the IETF standardized". I always thought that Microsoft made this > recommendation for using .local in violation of the RFC, like they > violate the CSS standard (one pixel off render bug), and the DHCP > standard (non-release at shutdown, continued use of an expired lease), > and some DNS standards (undocumented client fail-over). > > Can someone point me to the relevant IETF document, so I know what the > standard is?
My question needs to be amended, since I now understand that Microsoft and (somebody else) have published different RFCs, but that both define .local as a/the multicast TLD. Why does every installation of Microsoft Active Directory strongly recommend the use of .local as the TLD, when (1) there is no advantage to .local over .int, .lan, or .msft, (2) this will clearly invalidate ~both~ of the RFCs by using .local for unicast, and (3) there are partial implementations of .local as a multicast TLD in popular products (MacOS and SUSE, at least) and this practice causes those products to appear broken? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
