Thank you Stuart for your reply.
When I run named-checkconf seeing as below and also status shows always
failed.
I have looked into the below zones and not seen any issue with those.
[dev][root@xtld2.usiad42 log]# named-checkconf -z /etc/named.conf
zone localhost.localdomain/IN: loaded serial 0
zone localhost/IN: loaded serial 0
zone
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN:
loaded serial 0
zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
zone 0.in-addr.arpa/IN: loaded serial 0
[dev][root@xtld2.usiad42 log]# service named status
rndc: connect failed: 127.0.0.1#953: connection refused
● named.service - LSB:
start|stop|status|restart|try-restart|reload|force-reload DNS server
Loaded: loaded (/etc/rc.d/init.d/named; bad; vendor preset: disabled)
Active: failed (Result: timeout) since Fri 2021-04-09 04:49:29 UTC; 1h
15min ago
Docs: man:systemd-sysv-generator(8)
Process: 23987 ExecStop=/etc/rc.d/init.d/named stop (code=exited,
status=1/FAILURE)
Process: 1345 ExecStart=/etc/rc.d/init.d/named start (code=killed,
signal=TERM)
Apr 09 05:19:38 named[1354]: generating session key for dynamic DNS
Apr 09 05:19:38 named[1354]: could not create /var/run/named/session.key
Apr 09 05:19:38 named[1354]: failed to generate session key for dynamic
DNS: permi...ied
Apr 09 05:19:38 named[1354]: sizing zone task pool based on 583 zones
Apr 09 05:19:38 named[1354]: none:100: 'max-cache-size 90%' - setting to
115894MB ...MB)
Apr 09 05:19:39 named[1354]: none:100: 'max-cache-size 90%' - setting to
115894MB ...MB)
Apr 09 05:19:39 named[1354]: configuring command channel from
'/etc/rndc.key'
Apr 09 05:19:39 named[1354]: configuring command channel from
'/etc/rndc.key'
Apr 09 05:19:39 named[1354]: reloading configuration succeeded
Apr 09 05:19:39 named[1354]: zone
5.0.0.0.0.0.0.0.8.1.6.0.1.0.a.2.ip6.arpa/IN: ref...led
Hint: Some lines were ellipsized, use -l to show in full.
[dev][root@xtld2.usiad42 log]#
On Fri, Apr 9, 2021 at 11:16 AM Stuart@registry.godaddy
wrote:
>
>
> > From: bind-users on behalf of rams <
> brames...@gmail.com>
> > Date: Friday, 9 April 2021 at 2:56 pm
> > To: bind-users
> > 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
