Hi Eyal,
It might be too long. But maybe you could solve it by fixing
systemd-resolved or disabling it completely. systemd-resolved should
contact DNS as usual, all your aliases should work there unless
overriden in /etc/hosts.
If you do not want to systemd-resolved to interfere, disable it by:
$ (sudo) systemctl disable --now systemd-resolved
$ (sudo) rm /etc/resolv.conf
$ (sudo) ln -s /run/NetworkManager/resolv.conf /etc/resolv.conf
It would not provide split-DNS on VPN, but should always reach dns
module in /etc/nsswitch.conf in default configuration.
If you want to use it and fix it instead, resolvectl output would help
us guess what might be wrong with it.
Cheers,
Petr
On 7/18/21 3:18 AM, Eyal Lebedinsky wrote:
This was brought up before, but today again it bit me. There was a
glibc update (fc34)
which provides a new nsswitch.conf with this line
hosts: files myhostname resolve [!UNAVAIL=return] dns
which caused all the aliases I had for my server to fail because my
local dns was not looked up.
Had to again remove the '[!UNAVAIL=return]' stanza.
Is this issue being fixed? I found this
https://bugzilla.redhat.com/show_bug.cgi?id=1717384
which suggests nsswitch.conf will become a fedora file (not glibc) and
hopefully better, but this log
has now been open for a long time.
Regards
--
Petr Menšík
Software Engineer
Red Hat,
http://www.redhat.com/
email: pemensik(a)redhat.com
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB