After update..Job for bind9.service failed

Community Support
1

Job for bind9.service failed.
See “systemctl status bind9.service” and “journalctl -xe” for details.

any idea???

2

It starts correctly and after 5 min it crashes

3

Have you followed the instructions that you included in your first post? That’s where you will want to begin your diagnosis.

1 Like
4

Did you check?

systemctl status bind9.service and journalctl -xe

1 Like
5

captura
captura884×732 168 KB

6

captura1
captura11255×752 310 KB

7
  • NOTE: Hestia Control Panel in combination with OpenVZ 7 or lower might have issue Bind9 server not starting or issues with Firewall. If you use a Virtual Private Server we strongly advise you to use something based on KVM or LXC!
8

it’s a cloud by heztner

9

That is strange:

systemctl restart bind9
systemctl status bind9

Should show the reason why it fails to start

10

it starts and after 5 minutes it falls

captura
captura1132×375 128 KB

11

I found this in the syslog

Could it be a port problem?

Dec 26 11:30:05 mh2 systemd[1]: Stopping BIND Domain Name Server…
Dec 26 11:30:05 mh2 named[14196]: received control channel command ‘stop’
Dec 26 11:30:05 mh2 named[14196]: shutting down: flushing changes
Dec 26 11:30:05 mh2 named[14196]: stopping command channel on 127.0.0.1#953
Dec 26 11:30:05 mh2 named[14196]: stopping command channel on ::1#953
Dec 26 11:30:05 mh2 named[14196]: no longer listening on ::#53
Dec 26 11:30:05 mh2 named[14196]: no longer listening on 127.0.0.1#53
Dec 26 11:30:05 mh2 named[14196]: no longer listening on 162.55.XXX.XXX#53
Dec 26 11:30:05 mh2 named[14196]: exiting
Dec 26 11:30:05 mh2 systemd[1]: Stopped BIND Domain Name Server.
Dec 26 11:30:05 mh2 systemd[1]: bind9.service: Start request repeated too quickly.
Dec 26 11:30:05 mh2 systemd[1]: bind9.service: Failed with result ‘start-limit-hit’.
Dec 26 11:30:05 mh2 systemd[1]: Failed to start BIND Domain Name Server.
Dec 26 11:30:06 mh2 systemd[1]: bind9.service: Start request repeated too quickly.
Dec 26 11:30:06 mh2 systemd[1]: bind9.service: Failed with result ‘start-limit-hit’.

12

looks like something stops your bind9 service, but no idea what - you need to find that out somehow.

13

I already found and solved the problem, I had a dns-cluster in a VestaCP with a suspended domain which would not let me delete it, I deleted and created the dns-cluster again and everything is OK, the synchrony runs every 5 min, that’s why dns server down. Thank you

14

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