| 1 |
On 19/12/17 04:25, David Haller wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> On Mon, 18 Dec 2017, Michael Orlitzky wrote: |
| 5 |
>> On 12/18/2017 02:55 PM, Wol's lists wrote: |
| 6 |
>>> My router defaults, iirc, to .local. And I thought .home also did the |
| 7 |
>>> same sort of thing. |
| 8 |
>> |
| 9 |
>> Both are reserved: the ".home" TLD is reserved for the Home Networking |
| 10 |
>> Control Protocol in the RFC 7788 that you cited, and ".local" is |
| 11 |
>> reserved for some multicast DNS mumbo jumbo in RFC 6762. |
| 12 |
>> |
| 13 |
>> (There is no good choice, and out of the bad ones, ".local" is OK I guess.) |
| 14 |
>> |
| 15 |
>>> See RFCs 7788 for .home, and 8244 for .local |
| 16 |
>> |
| 17 |
>> I didn't know about RFC 8244 (it's from October), but it looks like it |
| 18 |
>> only points out the existing problems. I'll go read it. |
| 19 |
>> |
| 20 |
>>> I think .local was correctly added to 6761, so that domain CAN be used |
| 21 |
>>> as your private network's TLD. |
| 22 |
>> |
| 23 |
>> local doesn't appear in RFC 6761, you might be thinking of localhost? |
| 24 |
>> For ".localhost", the RFC more or less states that your users can assume |
| 25 |
>> that all addresses resolve to 127.0.0.1, which makes it unsuitable for a |
| 26 |
>> network with more than one machine. |
| 27 |
> |
| 28 |
> ISTR, .localdomain is the new .local... |
| 29 |
> |
| 30 |
> BTW: I hate it how .local got ursurped by zeroconf/mDNS. |
| 31 |
> |
| 32 |
> -dnh |
| 33 |
> |
| 34 |
|
| 35 |
I have used .localdomain for years without issue. VLANS |
| 36 |
(wifi.localdomain, lan.localdomain etc.) are great if you have the |
| 37 |
hardware to do it. |
| 38 |
|
| 39 |
Using non-official TLD internally shouldn't cause any problems (unless |
| 40 |
someone is "stupid"). |
| 41 |
|
| 42 |
BillK |
Archives