bind broken after zypper dup

English Applications
1

Hi,

Yesterday I went for “zypper dup” on my RPi4 that has tumbleweed installed and it broke my bind service running there. Bind package itself was not upgraded, so seems something with mounting rules or systemd has changed.

# systemctl status named
● named.service - Berkeley Internet Name Domain (DNS)
     Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Mon 2021-03-08 09:29:28 CET; 28min ago
    Process: 7527 ExecStart=/usr/sbin/named.init start (code=exited, status=226/NAMESPACE)


Mar 08 09:29:28 odzinsh systemd[1]: Starting Berkeley Internet Name Domain (DNS)...
Mar 08 09:29:28 odzinsh systemd[7527]: named.service: Failed to set up mount namespacing: /run/systemd/unit-root/etc/named.conf.include: No such file or directory
Mar 08 09:29:28 odzinsh systemd[7527]: named.service: Failed at step NAMESPACE spawning /usr/sbin/named.init: No such file or directory
Mar 08 09:29:28 odzinsh systemd[1]: named.service: Control process exited, code=exited, status=226/NAMESPACE
Mar 08 09:29:28 odzinsh systemd[1]: named.service: Failed with result 'exit-code'.
Mar 08 09:29:28 odzinsh systemd[1]: Failed to start Berkeley Internet Name Domain (DNS)

.

Some hints on how or where to proceed with troubleshooting are welcome.
Thanks,

2

I am not intimately familiar with bind, but my understanding is that it was switched from chroot jail to systemd protection, and named.service unconditionally lists files that are optional:

ReadWritePaths=/var/lib/named /var/run /etc/named.conf.include /etc/named.conf.include.BINDconfig

This probably should be

**-**/etc/named.conf.include **-**/etc/named.conf.include.BINDconfig

(note leading “-”) to indicate they may not exist.

Open bug report against bind.