>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.
--
Per Jessen, Zürich (1.5°C)
Member, openSUSE Heroes (2016 - present)
We're hiring - https://en.opensuse.org/openSUSE:Heroes
