On 2/27/23 06:56, Per Jessen wrote:
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 will look and follow-up with what I did, but I specifically configured how /etc/resolve.conf would be updated to prevent just this weirdness. What I don't recall is what I did (see post about grey beards...) On 15.4, I saw the same behavior, the major problem being an empty resolve.conf that screwed name resolution. What I found is resolve.conf is now more a punching-bag for the various network managers, and some don't use it at all anymore (therein lies the issue) So I configured it to maintain the domain and search config I wanted to it didn't mysteriously end up empty depending on what order or what mood the boot process was in. Will follow-up with the details, but no you are not crazy, and yes I saw the same behavior on 15.4. -- David C. Rankin, J.D.,P.E.