BIND DNS Server uninstalled - chroot issue on 1.999-x update

[Ilia]

Thanks for the provided info.

@keerby

My config file was rewritten just after updating to rev1 and rev2.

By saying this, do you mean after upgrading Webmin 1.999-1 to 1.999-2, correct?

How did you upgrade? Using package manager, like yum update command? Also, do you use Virtualmin on that system?

[Ilia]

I looked deeper into the code and it seems that theoretically it’s possible to have new directives merged into your existing configs. Although, at the moment I see this is only possible if your actual detected OS on Webmin config is incorrect. What is the output of the following command on your systems @jmunjr @keerby @DonX ?

grep os_ /etc/webmin/config

[jmunjr]

@Ilia

grep os_ /etc/webmin/config

grep os_ /etc/webmin/config
os_version=15.9
real_os_type=CentOS Linux
os_type=redhat-linux
real_os_version=7.9.2009

Thanks for sorting this out. As I stated, my system corrected itself, I think after I made a change in the module config to how chroot was handled, and then changing back, though I am not 100% sure about that.

[Ilia]

Alright, I see the cause of this issue. We will fix this on the next Webmin release.

Add further fixes to BIND configs

Sorry about that and thanks for reporting!

[DonX]

@Ilia just to note, I get the same output as jmunjr.

real_os_type=CentOS Linux
os_version=15.9
os_type=redhat-linux
real_os_version=7.9.2009

[Jamie]

@Ilia how does this patch fix the issue?

[Ilia]

@Jamie, it adds an empty chroot= and auto_chroot=, preventing copyconfig.pl from adding (merging) those values.

[Jamie]

Was a bug introduced when newer OS-specific config-* files were added recently?

[Ilia]

Yes, this issue doesn’t happen with 1.994 and it doesn’t happen with 1.999-3 (locally built). Moreover, it doesn’t happen with 1.999-2 if installed initially, however the issue pops up if you reinstall 1.999-2 using package manager like dnf reinstall webmin …

[reshhia]

Install Virtualmin on Centos 7 After updating BIND version 9.11, BIND does not start. ERROR : Failed to start BIND : sh: /etc/rc.d/init.d/named: No such file or directory

Output of grep os_ /etc/webmin/config

os_type=redhat-linux
os_version=15.9
real_os_type=CentOS Linux
real_os_version=7.9.2009

@Ilia Please let me know how to fix the issue or when will be updating the software.

Thank you

[Ilia]

@reshhia

@Ilia Please let me know how to fix the issue or when will be updating the software.

The fix for this issue would be as simple as running the following command over-writing existing Webmin Bind module config file:

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

[reshhia]

@Ilia

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

NO it’s not working still able to start bind its just install new server in the beginning have error to start a bind.

Failed to start BIND : sh: /etc/rc.d/init.d/named: No such file or directory

[jmunjr]

All is ok on my system. Thanks for the fixes. Appreciate you guys.

[reshhia]

I reinstall server multiple time every time BIND server not start @Ilia please fix it and update you software with new installation files. awaiting for good new.

@jmunjr I’m happy for you, but every new user name face this issue with CentOS Linux 7.9.2009.

I hope Virtualmin team will understand.

Thanks you!

[Ilia]

@reshhia

I reinstall server multiple time every time BIND server not start @Ilia please fix it and update you software with new installation files. awaiting for good new.

@jmunjr I’m happy for you, but every new user name face this issue with CentOS Linux 7.9.2009.

Thank you for the heads up. We can confirm that Webmin 1.999-2 has a bug that manifests itself on CentOS 7 in Webmin BIND module.

We will fix this in upcoming Webmin release.

Also, note that it’s not advised to install CentOS 7 in 2022 and AlmaLinux or Rocky Linux should be preferred!

[reshhia]

@Ilia

upcoming Webmin release.

When Upcoming Webmin release?

[Ilia]

@Ilia

We will fix this in upcoming Webmin release.

@reshhia

When Upcoming Webmin release?

We don’t have ETA.

@reshhia

NO it’s not working still able to start bind its just install new server in the beginning have error to start a bind.

[That shouldn’t be the case. Simply run the following command to fix a Webmin Bind config on CentOS 7:

The fix is here:

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.

[reshhia]

Unfortunately, Automated Virtualmin Installation not working with those OS AlmaLinux or Rocky Linux.

EDIT: Again reinstall centos 7 after your given comment bind and it’s not configured because after Setting Up Virtual Server, the domain not working. I’m very disappointeded with your support.

almost after wasting my 5 days still bind not working with Linux.

[Ilia]

AlmaLinux and Rocky Linux are supported using beta version of install.sh script. This has been discussed in multiple posts.

Again reinstall centos 7 after your given comment bind and it’s not configured because after Setting Up Virtual Server, the domain not working. I’m very disappointeded with your support.

If you need more help, please provide more details on what isn’t working exactly. You shouldn’t be using CentOS 7 with a clean install in 2022 anyway.

If you still want to do it on CentOS 7 system, use the command I mentioned above to replace a wrong config with the right one, and then run the following command to re-configure Bind for Virtualmin:

virtualmin-config-system -i=Bind

almost after wasting my 5 days still bind not working with Linux.

Sorry but this is Webmin category, and I had no idea it didn’t work for you on Virtualmin.

@reshhia

I reinstall server multiple time every time BIND server not start @Ilia please fix it and update you software with new installation files.

There is no reason to reinstall anything, this is not Windows 3.11. It’s the mater of a wrong config file for Bind Webmin module. Besides reinstalling would produce the same results, as Webmin package hasn’t been updated yet.