Hesia with also-notify bind9

Hallo.

Debian 10 with Hesia works just fine. My VPS provider has provided me ns1.namezone.ru / ns2.namesone.ru but as well says I need to set DNS BIND Zone Transfers.
I did all correct in /root/dnsmgr/dnsmgrupdate.conf

NAMEDPATH=/etc/bind/named.conf
MASTERIP=182.xxx.xxx.xxx
DNSMGRURL=https://dnsmgr1.server.net/manager/dnsmgr?out=text&authinfo=user:pass
DNSMGRURL=https://dnsmgr2.server.net/manager/dnsmgr?out=text&authinfo=user:pass
CHANGESONLY=yes
CHECKMASTER=yes

/etc/bind/named.conf

notify explicit;
also-notify { 74.xxx.xxx.xxx; 185.xxx.xxx.xxx; };
allow-transfer { 74.xxx.xxx.xxx; 185.xxx.xxx.xxx; };

Everything works just fine. What do you recommend:

  1. to make a cron and a script that should run every minute to check if there is a new domain (made in Cpanel Hestia)
    or
  2. “ask” Hestia to run the script every time a domain is made in the panel.

Also one question:
If I delete a domain name in Hestia why it is not deleted in DNS and MAIL options?

1 would probaly been easier to solve, but not sure if it is needed, usualy also-notify should do the job - but I do not know how exactly your providers requirements.

Probaly you mean deleting a webdomain does not remove dns and mail - this behaviour is expected. Because sometimes you want to delete a web, but no mail or dns (for example moving web to another server) - this would cause a data loss.

Cron job will do my day.
Deleting the whole project is 95% what we need when we press “delete” on domain name in VestaCP with warning “Mind you are to delete ALL files as well”. IMHO.

Big NO on that! To delete the DNS and Mail Domain separately is just clicking two more buttons. But if someone loses their DNS zone or Mail files, they will get into a lot of trouble for sure. And what’s more, only a few people read (and understand) warning messages, before clicking :zipper_mouth_face:

So as always better safe than sorry :slightly_smiling_face:

1 Like