In data lunedì 27 febbraio 2023 13:56:46 CET, Per Jessen ha scritto:
From the mythv thread - I have just repeated this issue, on Leap 15.1.
(I know its EOL, but I don't have a choice).
a) after rebuilding the initrd, the first boot - just the standard template in /etc/resolv.conf, no nameserver. firewalld is running.
b) 2nd reboot, no changes. Still an empty /etc/resolv.conf.
The wicked lease information is from last night.
c) stopped and disabled firewalld, 3rd reboot.
Now the lease info was updated and so was /etc/resolv.conf. Weird stuff.
d) enabled firewalld and rebooted. Empty /etc/resolv.conf.
I would try this out on 15.4 and 15.5, but NFS installations don't work. I guess I could do a zypper dup.
Anyone have any suggestion as to how or why firewalld might interfere with the populating of /etc/resolv.conf ?? Surely that's crazy.
I did encounter this on 15.1 at the time (way back in time BTW). What helped with me (the only thing that did help) was to erase etc/ resolv.conf and reboot. I never found out what cause this, sorry. But this could (not guarantee) help.