https://bugzilla.suse.com/show_bug.cgi?id=1186278 https://bugzilla.suse.com/show_bug.cgi?id=1186278#c3 Josef M�llers <josef.moellers@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #3 from Josef M�llers <josef.moellers@suse.com> --- Hello Peter, Long time no hear ;-) Must have been at least 5 years! The bind-9.16.15-2.1 in TumbleWeed had been a premature submission, I'm really sorry for that. We have changed bind from running inside a chroot jail to protecting it (or the rest of the system, depending upon the point of view) using systemd's protection mechanisms. During this, we decided to do some additional cleanup. Therefore the /etc/named.conf.include file is not used and therefore not created anymore and the createNamedConfInclude script is not used any more. While we have strived to make transition from the chroot environment to the systemd protection as sound as possible, at least in the very first releases, this was bumpy, to say the least. First of all: thanks for spotting the missing $ sign. It was still missing when you reported this, so this is now fixed. The issue with the "-d 9", I cannot reproduce. On a TW VM, named starts OK and "ps aux | fgrep named" as well as the "Process:"-line for the "ExecStart=" do show that the full contents of NAMED_ARGS has been applied. Also, "named" still honors it, so I'm unsure how this has happened. The new /etc/sysconfig/named will have only these three entries: NAMED_INITIALIZE_SCRIPTS="" RNDC_KEYSIZE="512" NAMED_ARGS="" If you want to, I could attach the latest TW build here. Otherwise please wait for the next TW release. Thanks again and stay safe! -- You are receiving this mail because: You are on the CC list for the bug.