1 |
On Sun, Apr 3, 2022 at 4:25 AM Alexander Puchmayr |
2 |
<alexander.puchmayr@×××××××.at> wrote: |
3 |
> |
4 |
> wasn't systemd per se, it was an update of /etc/nsswitch.conf. The old version |
5 |
> had |
6 |
> |
7 |
> Hosts: mymachines files myhostname dns |
8 |
> |
9 |
> while the new version contains |
10 |
> |
11 |
> Hosts: mymachines resolve [!UNAVAIL=return] files myhostname dns |
12 |
> |
13 |
> The extra "resolve [!UNAVAIL=return]" makes the difference. It loads the |
14 |
> glibc's plugin nss-resolve [1], which then calls systemd-resolved [2], which |
15 |
> interprets '.local' as mDNS address. The mDNS is not activated on purpose, it |
16 |
> seems to be some default setting of the router which does not appear in the |
17 |
> configuration pages (or I didn't find it). |
18 |
|
19 |
So, the nsswitch file does direct glibc to use the systemd resolve |
20 |
library, but it is resolved that is using mDNS. Did you check your |
21 |
resolved.conf? Does it have MulticastDNS=no set? If it isn't |
22 |
explicitly set you'd probably need to check the build-time options for |
23 |
what the defaults are these days. |
24 |
|
25 |
I don't see how your router would impact this. You don't even need |
26 |
DHCP/DNS at all to use mDNS, as long as the hosts implement mDNS and |
27 |
link-local autoconfig. (Those are addresses in the range |
28 |
169.254.0.0/16 and fe80::/10. Many OSes support this at this point by |
29 |
default.) |
30 |
|
31 |
In any case, disabling resolved would certainly solve the issue, but |
32 |
if you want to still use it you can fine-tune the mDNS settings on it. |
33 |
|
34 |
-- |
35 |
Rich |