Hello,
On Mon, 18 Dec 2017, Michael Orlitzky wrote:
>On 12/18/2017 02:55 PM, Wol's lists wrote:
>> My router defaults, iirc, to .local. And I thought .home also did the
>> same sort of thing.
>
>Both are reserved: the ".home" TLD is reserved for the Home Networking
>Control Protocol in the RFC 7788 that you cited, and ".local" is
>reserved for some multicast DNS mumbo jumbo in RFC 6762.
>
>(There is no good choice, and out of the bad ones, ".local" is OK I guess.)
>
>> See RFCs 7788 for .home, and 8244 for .local
>
>I didn't know about RFC 8244 (it's from October), but it looks like it
>only points out the existing problems. I'll go read it.
>
>> I think .local was correctly added to 6761, so that domain CAN be used
>> as your private network's TLD.
>
>local doesn't appear in RFC 6761, you might be thinking of localhost?
>For ".localhost", the RFC more or less states that your users can assume
>that all addresses resolve to 127.0.0.1, which makes it unsuitable for a
>network with more than one machine.
ISTR, .localdomain is the new .local...
BTW: I hate it how .local got ursurped by zeroconf/mDNS.
-dnh
--
[the role of government] is not taking over the health care system, that has
existed for a long long time and has produced the best health records in the
world ... -- Mitt Romney, 2012, first presidential candidate debate,
who clearly never has seen "Sicko" by Michael Moore
