Bind9 restart failed when deleting mail domain or issuing ssl

[Leonk]

Hello guys.

I have the error eveytime i issue SSL or delete mail domain.

/usr/local/hestia/bin/v-add-letsencrypt-domain user ``example.com`` ``www.example.com
Error: bind9 restart failed’
Error: 20
/usr/local/hestia/func/main.sh: line 123: [: dns failed to restart: integer expression expected
/usr/local/hestia/func/main.sh: line 184: exit: dns failed to restart: numeric argument required

and

/usr/local/hestia/bin/v-delete-mail-domain user
Error: bind9 restart failed’
Error: bind9 restart failed’

by the way ssl is issued successfully and everything is working. but i want to understand whats going on because everything was good.

this is the syslog:

2026-04-24T11:17:18.401323+03:00 panel named[3987307]: received control channel command ‘reconfig’
2026-04-24T11:17:18.402517+03:00 panel named[3987307]: loading configuration from ‘/etc/bind/named.conf’
2026-04-24T11:17:18.402654+03:00 panel named[3987307]: the working directory is now ‘/var/cache/bind’
2026-04-24T11:17:18.435923+03:00 panel named[3987307]: /etc/bind/named.conf:1090: zone ‘``example.com``’: already exists previous definition: /etc/bind/named.conf:1089
2026-04-24T11:17:18.437072+03:00 panel named[3987307]: /etc/bind/named.conf:1168: zone ‘``example1.com``’: already exists previous definition: /etc/bind/named.conf:1167
2026-04-24T11:17:18.437524+03:00 panel named[3987307]: /etc/bind/named.conf:1207: zone ‘``example2.org``’: already exists previous definition: /etc/bind/named.conf:1206
2026-04-24T11:17:18.438589+03:00 panel named[3987307]: /etc/bind/named.conf:1247: zone ‘``example3.org``’: already exists previous definition: /etc/bind/named.conf:1246
2026-04-24T11:17:18.438996+03:00 panel named[3987307]: /etc/bind/named.conf:1276: zone ‘``example4.com``’: already exists previous definition: /etc/bind/named.conf:1275
2026-04-24T11:17:18.439121+03:00 panel named[3987307]: /etc/bind/named.conf:1286: zone ‘``example5.org``’: already exists previous definition: /etc/bind/named.conf:1285
2026-04-24T11:17:18.444850+03:00 panel named[3987307]: reloading configuration failed: failure
2026-04-24T11:17:18.476487+03:00 panel named[3987307]: received control channel command ‘reload ``example6.co.uk``’
2026-04-24T11:17:18.518325+03:00 panel named[3987307]: received control channel command ‘notify ``example6.co.uk``’
2026-04-24T11:17:32.463295+03:00 panel systemd[1]: Stopping nginx.service - nginx - high performance web server…
2026-04-24T11:17:33.171860+03:00 panel systemd[1]: nginx.service: Deactivated successfully.
2026-04-24T11:17:33.172558+03:00 panel systemd[1]: Stopped nginx.service - nginx - high performance web server.
2026-04-24T11:17:33.173027+03:00 panel systemd[1]: nginx.service: Consumed 8.643s CPU time.
2026-04-24T11:17:33.190997+03:00 panel systemd[1]: Starting nginx.service - nginx - high performance web server…

of course i read:

Bind9 restart failed

I solved it, failure to load bind9 was due to AppArmor … I finally decided to set all AppArmor profiles to “complain” mode, until I have the time to properly debug it.

ERROR: Restart of bind9 failed

Fix Fail2ban by reinstall and chainging vsftpd-iptables to - true to false apt-get remove --purge fail2ban -y apt-get install fail2ban -y systemctl restart fail2ban [vsftpd-iptables] enabled = false filter = vsftpd action = hestia[name=FTP] logpath = /var/log/vsftpd.log maxretry = 5

Error: ERROR: Restart of bind9 failed

Check /etc/bind/named.conf.options on line 2 …

but seems my case is a bit different.

yesterday I deleted 600+ mail domains which is not needed for me but was created when adding domains. (some domains did not exist already at all but had mail domain)

P.S. by the way: is there a way to add domain without mail domain?

[sahsanu]

Hi,

For some reason you have duplicated zones in /etc/bind/named.conf that you should remove.

Show the output of these commands:

named-checkconf
systemctl restart named
systemctl status named --no-pager -l

@Leonk

is there a way to add domain without mail domain?

Do you mean mail records in DNS? If so, you can create a new DNS template and remove the mail and webmail A records, as well as the MX record, from that template.

The DNS templates are located at /usr/local/hestia/data/templates/dns/, and you can use default.tpl as a base to create your new template.

Then, you should edit the package you use for your users (or create a new one), replace the default DNS template with the one you created, and that’s it.

Use that package when creating new users or applying it to existing ones, and the mail records won’t be created automatically when adding a DNS domain.

[Leonk]

@sahsanu

named-checkconf
/etc/bind/named.conf:1090: zone ‘``ex1.com``’: already exists previous definition: /etc/bind/named.conf:1089
/etc/bind/named.conf:1168: zone ‘``ex2.com``’: already exists previous definition: /etc/bind/named.conf:1167
/etc/bind/named.conf:1207: zone ‘``ex3.org``’: already exists previous definition: /etc/bind/named.conf:1206
/etc/bind/named.conf:1247: zone ‘``ex4.org``’: already exists previous definition: /etc/bind/named.conf:1246
/etc/bind/named.conf:1276: zone ‘``ex6.com``’: already exists previous definition: /etc/bind/named.conf:1275
/etc/bind/named.conf:1286: zone ‘``ex5.org``’: already exists previous definition: /etc/bind/named.conf:1285

Failed to start named.service - BIND Domain Name Server.