| 1 |
>>-----Original Message----- |
| 2 |
>>From: Rich Freeman <rich0@g.o> |
| 3 |
>>Sent: Tuesday, January 18, 2022 11:41 AM |
| 4 |
>>To: gentoo-user@l.g.o |
| 5 |
>>Subject: Re: [gentoo-user] TLD for home LAN? |
| 6 |
>> |
| 7 |
>>On Tue, Jan 18, 2022 at 12:28 PM Laurence Perkins <lperkins@×××××××.net> wrote: |
| 8 |
>>> |
| 9 |
>>> 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. |
| 10 |
>> |
| 11 |
>>If a host queries DNS first, and obtains an NXDOMAIN from an authoritative name server, I'm not sure most would even check mDNS. I think I had that issue back when I was using .local before I heard of zeroconfig. |
| 12 |
>> |
| 13 |
|
| 14 |
Right. If you have .local names registered with your DNS, but not resolvable via mDNS, then if you plug in a device which tries to assign a conflicting name and it only checks mDNS for conflicts (the standard only *says* to check mDNS for conflicts, even though checking DNS as well would seem to always be a good idea) you could end up with DNS and mDNS returning different results. This can be confusing if different devices have different resolver preference orders.
|
| 15 |
|
| 16 |
So, if you're going to have your DNS resolve .local names it's a really good idea to provide those names via mDNS as well. At least if there's any significant chance of a conflict arising.
|
| 17 |
|
| 18 |
LMP |
Archives