Problems with configuration after upgrade

[karlism]

Hello,

After seemingly successful upgrade of facileManager to 2.3 and fmDNS module to 2.2.4, I now experience two issues with server configuration building:

As you can see, there are two errors, about 13th line of /etc/named.conf.key, even though this line is actually empty, and about nonexistent /var/named directory. BIND is running chrooted in my case and both /var/named and /var/named/chroot/var/named directories exist.

Any ideas what could be wrong?
Thanks!

[WillyXJ]

Hi,

That is indeed odd behavior. The syntax checks are performed by the BIND named-checkconf utility. Did you upgrade BIND recently, too? What version of BIND are you using?

[karlism]

Thank you for prompt reply!

I'm using bind-chroot package 9.9.4-29.el7_2.3 on CentOS 7.2. Judging by yum logs, BIND package hasn't been upgraded since May 27th, so I suspect that's not an issue.

[WillyXJ]

I've found the issue with $fm_module_buildconf->namedSyntaxChecks() which only impacts the syntax check routine. If you disable the checks, config builds and zone reloads are successful. A fix will be coming in the next bug fix release.

[karlism]

Thanks!