> From: bind-users <bind-users-boun...@lists.isc.org> on behalf of rams
> <brames...@gmail.com>
> Date: Friday, 9 April 2021 at 2:56 pm
> To: bind-users <bind-users@lists.isc.org>
> Subject: Unable to start name
> Hi
> We are using bind 9.11.28.1 on centos7.8. We have large number of zones
> on disk. When we stop/start , we are not getting successful message and
> seeing below error. But in log we see named is running and doing
> axfr/ixfr. Do we need to add any configuration paameter to avoid below
> error.
>
> Starting named (via systemctl): Job for named.service failed because a
> timeout was exceeded. See "systemctl status named.service" and "journalctl
> -xe" for details
You mentioned that you have a large number of zones. If there are no error
messages generated by NAMED starting other than the exceeding of a timeout,
it could just be the system service-start timing out.
Have a look at TimeoutSec in the service unit definition:
https://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutSec=
You may also want to try "named-checkconf -z /etc/named.conf" and see how long
it takes (as this does a similar sort of validation as starting the service
does).
Stuart
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
