NAMED reported as not running but it seems to be running

[Dim_Git]

|Operating system |CentOS Linux 7.9.2009|
|Webmin version |2.001|
|Usermin version |1.860|
|Virtualmin version |7.2 |
|Authentic theme version |20.01.1:5 |
BIND version 9.11
NOTE: This server only runs as a secondary name server.

Hi Everyone.

I have just run the updates and have run into errors with BIND. (I usually leave updates a week or so just in case they have some error which is corrected before I finally update.) The errors have onlt become apparent since the reboot. I have not made any changes to BIND that I can think of.

YUM log shows the following was updated

 Oct 04 04:57:44 Updated: webmin-2.001-1.noarch
 Oct 04 04:57:44 Updated: systemd-libs-219-78.el7_9.7.x86_64
 Oct 04 04:57:46 Updated: systemd-219-78.el7_9.7.x86_64
 Oct 04 04:57:46 Updated: rsync-3.1.2-11.el7_9.x86_64
 Oct 04 04:57:46 Updated: systemd-python-219-78.el7_9.7.x86_64
 Oct 04 04:57:47 Updated: systemd-sysv-219-78.el7_9.7.x86_64
 Oct 04 04:57:47 Updated: tuned-2.11.0-12.el7_9.noarch
 Oct 04 04:57:57 Updated: 3:wbm-virtual-server-7.2.gpl-1.noarch
 Oct 04 04:58:04 Updated: usermin-1.860-1.noarch
 Oct 04 04:58:06 Updated: ca-certificates-2022.2.54-74.el7_9.noarch
 Oct 04 04:58:07 Updated: tzdata-2022c-1.el7.noarch

This update required a reboot.

I note that on the dashboard server status it shows that BIND is not running. Clicking on the start button does not report any error or start the service.

Running systemctl status named returns the following which to me suggests that it is running.

 named.service - Berkeley Internet Name Domain (DNS)
    Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
    Active: active (running) since Tue 2022-10-04 05:13:10 GMT; 57min ago
   Process: 1207 ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} $OPTIONS (code=exited, status=0/SUCCESS)
   Process: 1192 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=0/SUCCESS)
  Main PID: 1210 (named)
    CGroup: /system.slice/named.service
            └─1210 /usr/sbin/named -u named -c /etc/named.conf

If I use one of the many DNS testing services to test a domain they don’t return any error on either primary or secondary DNS and domains still test out ok.

If I create a VS in this server to test I get the following errors
Adding new virtual website …
.. DNS domain failed! : Failed to open /var/named/chroot/var/named/dummytest.co.uk.hosts for writing : No such file or directory
and
.. Apache website failed! : Failed to open /var/named/chroot/var/named/dummytest.co.uk.hosts for writing : No such file or directory

If I go to Webmin > Servers > BIND DNS Server there is a message at the top saying

**Warning : The chroot directory /var/named/chroot that Webmin thinks BIND is using may be incorrect. The zone files for 2 domains could not be found.**

**Make sure that the chroot directory is set correctly on the [module configuration](https://ns1.ecsweb-dns.co.uk:10000/config.cgi?bind8) page.**

These domains appear to be the domains I set up in order to track this error down. I did delete them in Vmin “disable and delete” but they still show on this page.

I have spent some more time checking various things but can’t remember all of them and don’t want to overload this post.

[Dim_Git]

Updated to add

I looked at the configuration for the bind module and I see that this is not the same as another server (not yet updated) . This looks totally different.

FURTHER UPDATED TO ADD
I have since found another post about a similar sounding error which suggests running thsi command

cp /usr/libexec/webmin/bind8/config-CentOS-Linux-6.0-7.0 /etc/webmin/bind8/config

But I’m not sure that this also applies to my situation. I have another server that should be updated but don’t want to do that in case I get the same error so it would be great to know if running that command wouold fix the error.

Thanks and sorry to be a pain.

Tim

[Ilia]

Hello,

This is a known bug. The work around for now is to just install package upgrades and manually fix Webmin BIND module config (i.e. /etc/webmin/bind8/config) as described on the post below.

Please note that this bug is pretty harmless as it doesn’t affect BIND system service, as it only affects Webmin BIND module config.

CentOS 7: Unable to start BIND after Webmin update

Nevermind. I think I still see an issue here for users who has never saved Webmin Bind module config. Anyone with CentOS 7 needs to make sure that /etc/webmin/bind8/config file has the following directives added at the end of the file before installing Webmin 2.001 upgrade: auto_chroot= chroot= We will try to fix that issue for 2.002 release.

[Dim_Git]

Thanks for your time Illia.

I did do a search of the forum but failed to spot that post.

Apologies for wasting your time.