Bind not start on reboot

1

This can be fix with " systemctl enable named or ?

Thank you

2

You must first find out why the service is not starting.

Check whether the service is enabled:

systemctl is-enabled named

Reboot the server and immediately check the service and the log:

systemctl status named --no-pager -l
grep named /var/log/syslog | tail -n50
1 Like
3

Yes, running systemctl enable named will ensure BIND starts automatically on reboot.

if BIND still doesn’t start after enabling the service you might be running into a system-level issue related to networking or binding permissions. I had a similar issue in the past and resolved it by adding the following to /etc/sysctl.conf:

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv4.ip_nonlocal_bind = 1
vm.overcommit_memory = 1

After saving, run sysctl -p to apply the changes, then try rebooting and see if BIND starts as expected.

Let me know how it goes.