Am 26.04.20 um 23:42 schrieb R. Scott Bailey: Dear Scott,
> Life was good on my DNS server until my recent update to 9.16.2-3. > After upgrading, the exact configuration that was happy now fails to > start. Example: > > # named -g -u bind > 26-Apr-2020 17:25:50.921 Could not open '//run/named/named.pid'. > 26-Apr-2020 17:25:50.921 Please check file and directory permissions or > reconfigure the filename. > 26-Apr-2020 17:25:50.921 could not open file '//run/named/named.pid': > Permission denied > 26-Apr-2020 17:25:50.921 generating session key for dynamic DNS > 26-Apr-2020 17:25:50.929 Could not open '//run/named/session.key'. > 26-Apr-2020 17:25:50.929 Please check file and directory permissions or > reconfigure the filename. > 26-Apr-2020 17:25:50.929 could not open file '//run/named/session.key': > Permission denied > 26-Apr-2020 17:25:50.929 could not create //run/named/session.key > 26-Apr-2020 17:25:50.929 failed to generate session key for dynamic DNS: > permission denied /run/named should be created by tmpfiles, see /usr/lib/tmpfiles.d/named.conf . What does "ls -la /run/named" show? > 26-Apr-2020 17:25:50.929 sizing zone task pool based on 29 zones > 26-Apr-2020 17:25:50.933 could not configure root hints from > '/usr/share/dns/root.hints': permission denied> 26-Apr-2020 17:25:50.957 > loading configuration: permission denied That one is supposed to be world-readable... Do you have any denials from AppArmor in your kernel messages? I have upgraded several machines from 9.11 to 9.16 and they generally worked fine. Bernhard
