| 1 |
On 12/18/2017 02:55 PM, Wol's lists wrote: |
| 2 |
> |
| 3 |
> My router defaults, iirc, to .local. And I thought .home also did the |
| 4 |
> same sort of thing. |
| 5 |
|
| 6 |
Both are reserved: the ".home" TLD is reserved for the Home Networking |
| 7 |
Control Protocol in the RFC 7788 that you cited, and ".local" is |
| 8 |
reserved for some multicast DNS mumbo jumbo in RFC 6762. |
| 9 |
|
| 10 |
(There is no good choice, and out of the bad ones, ".local" is OK I guess.) |
| 11 |
|
| 12 |
|
| 13 |
> See RFCs 7788 for .home, and 8244 for .local |
| 14 |
|
| 15 |
I didn't know about RFC 8244 (it's from October), but it looks like it |
| 16 |
only points out the existing problems. I'll go read it. |
| 17 |
|
| 18 |
|
| 19 |
> I think .local was correctly added to 6761, so that domain CAN be used |
| 20 |
> as your private network's TLD. |
| 21 |
|
| 22 |
local doesn't appear in RFC 6761, you might be thinking of localhost? |
| 23 |
For ".localhost", the RFC more or less states that your users can assume |
| 24 |
that all addresses resolve to 127.0.0.1, which makes it unsuitable for a |
| 25 |
network with more than one machine. |
Archives