| 1 |
-----Original Message-----
|
| 2 |
From: tastytea <gentoo@××××××××.de>
|
| 3 |
Sent: Saturday, January 15, 2022 2:54 AM
|
| 4 |
>To: gentoo-user@l.g.o |
| 5 |
>Subject: Re: [gentoo-user] TLD for home LAN? |
| 6 |
> |
| 7 |
>On 2022-01-15 10:33+0000 Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 8 |
> |
| 9 |
>> Hello list, |
| 10 |
>> |
| 11 |
>> Rich F said recently, "I'd avoid using the .local TLD due to RFC |
| 12 |
>> 6762." |
| 13 |
>> |
| 14 |
> |
| 15 |
|
| 16 |
Glancing at that RFC, if you want to be compliant (which, it's *your* network, and this is all link-local only, so there's no reason you *have* to be), all you need to do is make sure that any .local addresses you assign are resolvable via multicast DNS.
|
| 17 |
|
| 18 |
The standard does not prohibit the names being resolvable via unicast DNS as well, though it does recommend that you make sure the two resolution paths return consistent results since most systems will take the first response they get.
|
| 19 |
|
| 20 |
If you assign .local addresses which aren't resolvable via mdns then there is the possibility that some piece of software will only check mdns and not regular dns before grabbing a name and cause a conflict. But as long as it's your network and your devices that's not terribly hard to sort out should it ever happen.
|
| 21 |
|
| 22 |
LMP |
Archives