BIND down when disabling a Virtual Server

SYSTEM INFORMATION
OS type and version CentOS Linux 7.9.2009
Webmin version 2.013
Virtualmin version 7.5

Hi

When disabling a Virtual Server, the DNS zone change it´s name adding .disabled after the domain name.
After that, BIND cannot start unless I delete the zone.

¿How can I fix this?

Thanks!!
Ignacio

What are the actual errors when restarting BIND?

Hi Joe

I disabled test.com.

When restarting bind this is the error:

Fallo al arrancar BIND: Redirecting to /bin/systemctl start named.service Job for named.service failed because the control process exited with error code. See “systemctl status named.service” and “journalctl -xe” for details.

Running journalctl -xe | grep named:

Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:2: ignoring out-of-zone data (test.com.lince.avnam.net)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:8: ignoring out-of-zone data (test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:9: ignoring out-of-zone data (test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:10: ignoring out-of-zone data (test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:11: ignoring out-of-zone data (www.test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:12: ignoring out-of-zone data (ftp.test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:13: ignoring out-of-zone data (m.test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:14: ignoring out-of-zone data (localhost.test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:15: ignoring out-of-zone data (webmail.test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:16: ignoring out-of-zone data (admin.test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:17: ignoring out-of-zone data (mail.test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:18: ignoring out-of-zone data (test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:19: ignoring out-of-zone data (test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:20: ignoring out-of-zone data (_dmarc.test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:21: ignoring out-of-zone data (*.test.com.disabled)
Feb 17 10:29:16 lince.avnam.net bash[4320]: /var/named/test.com.lince.avnam.net.hosts:22: ignoring out-of-zone data (2020._domainkey.test.com.disabled)
Feb 17 10:29:16 lince.avnam.net systemd[1]: named.service: control process exited, code=exited status=1
– Subject: Unit named.service has failed
– Unit named.service has failed.
Feb 17 10:29:16 lince.avnam.net systemd[1]: Unit named.service entered failed state.
Feb 17 10:29:16 lince.avnam.net systemd[1]: named.service failed.

Stale .bak files are nothing new on my system. When setting this current system up I used them regularly in the directory the zonefiles are located in. Yeah, I’d get errors saying they were ignored, but yeah, they were ignored and bind moved on. The looping is strange. Maybe something in the RH thinking that makes it fail so you fix it?

I think that’s a red herring. It doesn’t prevent BIND from starting…it’s ignoring the files. So, the question is, why is it actually not starting? I think we need more information…

More info.

Output from named.run whehj disabling test.com:


received control channel command ‘reload test.com.dylan.ar’
/var/named/test.com.dylan.ar.hosts:8: ignoring out-of-zone data (test.com.disabled)
/var/named/test.com.dylan.ar.hosts:9: ignoring out-of-zone data (test.com.disabled)
/var/named/test.com.dylan.ar.hosts:10: ignoring out-of-zone data (test.com.disabled)
/var/named/test.com.dylan.ar.hosts:11: ignoring out-of-zone data (www.test.com.disabled)
/var/named/test.com.dylan.ar.hosts:12: ignoring out-of-zone data (ftp.test.com.disabled)
/var/named/test.com.dylan.ar.hosts:13: ignoring out-of-zone data (m.test.com.disabled)
/var/named/test.com.dylan.ar.hosts:14: ignoring out-of-zone data (localhost.test.com.disabled)
/var/named/test.com.dylan.ar.hosts:15: ignoring out-of-zone data (webmail.test.com.disabled)
/var/named/test.com.dylan.ar.hosts:16: ignoring out-of-zone data (admin.test.com.disabled)
/var/named/test.com.dylan.ar.hosts:17: ignoring out-of-zone data (mail.test.com.disabled)
/var/named/test.com.dylan.ar.hosts:18: ignoring out-of-zone data (test.com.disabled)
/var/named/test.com.dylan.ar.hosts:19: ignoring out-of-zone data (test.com.disabled)
/var/named/test.com.dylan.ar.hosts:20: ignoring out-of-zone data (_dmarc.test.com.disabled)
/var/named/test.com.dylan.ar.hosts:21: ignoring out-of-zone data (*.test.com.disabled)
/var/named/test.com.dylan.ar.hosts:22: ignoring out-of-zone data (2020._domainkey.test.com.disabled)
zone test.com.dylan.ar/IN: has no NS records
zone test.com.dylan.ar/IN: not loaded due to errors.
received control channel command ‘stop’
shutting down: flushing changes
stopping command channel on 127.0.0.1#953
stopping command channel on ::1#953
no longer listening on ::#53
no longer listening on 127.0.0.1#53
no longer listening on 45.162.168.89#53
exiting


Thanks Joe

I forgot to tell. The only way to hace BIND running again is deleting the zone test.com.disabled.

But when I did this it listed it once and moved on. My question is why the loop? Is this Redhat’s way of making you deal with the error?

I dont´know where is the loop!!

My only guess, and a guess it is, is that Redhat’s configuration does some error checking and refuses to start on any error. One of the first things I do when I edit stuff by hand is to make a .bak file for disaster recovery so I just saw this recently. Gave the warning once and moved on.

Hm… Can’t recreate it now, maybe because it is now set up as a slave and ignoring the local config.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.