Bind9 dns server

1

i just installed hestiacp v1.4.12 on a clean ubuntu 20.04 server

  • the bind9 not starting
  • systemctl status bind9
    bind9.service - LSB: Start and stop bind9
    Loaded: loaded (/etc/init.d/bind9; generated)
    Active: active (exited) since Fri 2021-08-27 15:35:33 CEST; 10s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 16395 ExecStart=/etc/init.d/bind9 start (code=exited, status=0/SUCCESS)

Aug 27 12:43:25 .com systemd[1]: Stopping LSB: Start and stop bind9…
Aug 27 12:43:26 .com systemd[1]: bind9.service: Succeeded.
Aug 27 12:43:26 .com systemd[1]: Stopped LSB: Start and stop bind9.
Aug 27 15:35:33 .com systemd[1]: Starting LSB: Start and stop bind9…
Aug 27 15:35:33 .com systemd[1]: Started LSB: Start and stop bind9.

2

Try to start bind9? Check for any error output? Have a look at syslog?

We can’t do the debug work for you :slight_smile:.

3

alright thank u

4

Hi, I am also having the same issue with same OS (Ubuntu 20.04 server). I tried re-installing bind9 and the issue still persists. No error information on any of the logs, it just starts and stops. Did you find the solution to this? Let me know. Thanks.

5

Same issue here on a fresh 1blu VPS Ubuntu 20.04 install. No error in syslog, nothing configured at all. Tried changing the hosts but no change either.

Tried debian 11, same issue.

No idea what to do lol. Is this some kinda weird special bug? Don’t know if it has to do with the network or hostname setup maybe?

Here are some more infos:
service bind9 restart puts this in syslog

May 19 12:16:34 hestiaserver systemd[1]: Stopping LSB: Start and stop bind9...
May 19 12:16:34 hestiaserver systemd[1]: bind9.service: Succeeded.
May 19 12:16:34 hestiaserver systemd[1]: Stopped LSB: Start and stop bind9.
May 19 12:16:34 hestiaserver systemd[1]: Starting LSB: Start and stop bind9...
May 19 12:16:34 hestiaserver systemd[1]: Started LSB: Start and stop bind9.

bind9 status shows:

● bind9.service - LSB: Start and stop bind9
     Loaded: loaded (/etc/init.d/bind9; generated)
     Active: active (exited) since Thu 2022-05-19 12:16:34 UTC; 1min 9s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 9101 ExecStart=/etc/init.d/bind9 start (code=exited, status=0/SUCCESS)

May 19 12:16:34 hestiaserver systemd[1]: Starting LSB: Start and stop bind9...
May 19 12:16:34 hestiaserver systemd[1]: Started LSB: Start and stop bind9.
6

And journalctl -xe

7

Like to try it out but honestly I think it simply was a Virtuozzo misconfiguration (probably with the networking) that I couldn’t change. I cancelled that VPS and got a different one, everything working there.

8

There is an bug with OpenVZ …

9

The latest update, disabling temp iptables did the magic.
Done all updates and turn on iptables again, it works!

10

Something similar happens in Debian 12.
SERVICE →
bind9.service - LSB: Start and stop bind9
Loaded: loaded (/etc/init.d/bind9; generated)

  • Stopping bind9.service - LSB: Start and stop bind9…
  • bind9.service: Deactivated successfully

But the service is actually in /lib/systemd/system/named.service

So I decided to create a symbolic link to that path and bind9 runs without problems, but obviously that’s not the solution.

another solution is to copy “named.service” and rename it as bind9.service,

then systemctl daemon-reload
and systemctl start bind9