On Sun, Apr 3, 2022 at 4:25 AM Alexander Puchmayr
wrote:
>
> wasn't systemd per se, it was an update of /etc/nsswitch.conf. The old version
> had
>
> Hosts: mymachines files myhostname dns
>
> while the new version contains
>
> Hosts: mymachines resolve [!UNAVAIL=return] files
Thanks for the hint with mDNS, I wasn't aware of that. I'm using the '.local'
domain for all my machines for more than 15 years now, longer than mDNS
exists, but finally, after some research I found the problem, and actually it
wasn't systemd per se, it was an update of /etc/nsswitch.conf. The
On Sat, Apr 2, 2022 at 5:22 PM Alexander Puchmayr
wrote:
>
> ## portage.local maps to 192.168.1.6
> ## DNS-Server provided via DHCP is 192.168.1.1 (openwrt-router)
>
> buildhost-desktop ~ # ping portage.local
> ping: portage.local: Temporary failure in name resolution
>
>Protocols:
Hi,
After upgrading systemd from 249.9 to 249.11, some of my host names defined in
my router's host file do no longer resolve, but nslookup can still resolve
them properly. With 249.9 everything works fine, and all other machines which
did not yet get the update work fine.
Any ideas?
Thanks,
4 matches
Mail list logo
