Chroot Bind failed to start

[Paul Amaral]

Neverminded, I was able to traceback my steps and realize a fat fingered a
DNS entry in one of the zones,  added two periods to an authoritative zone’
s DNS record, causing bind to fail to start. The concerning issue was there
was no error on the logs at all, making it hard to figure out the issue.



Which leads me to the next question, let’s say I’m authoritative for
regular zone ABC.com and I fat fingered its DNS record, ns1..something.com.
Why would this affect the bind instance from starting up? Like I said there
was nothing on the logs and I understand that might be due to the Centos PKG
itself. Just wondering why that mistake down bind down and how I can get
more meaningful logs on the logs even those a prepackaged bind version.



TIA

Paul





From: bind-users <bind-users-bounces at lists.isc.org> On Behalf Of Paul Amaral
via bind-users
Sent: Tuesday, March 15, 2022 9:08 AM
To: 'bind-users at lists.isc.org' <bind-users at isc.org>
Subject: Chroot Bind failed to start



Hi, I realize this is related to Centos, but all the sudden chroot bind
failed to start up with any meaningful errors.

Anyone know what might be the issue here? I have no clues on that the issue
is.



Paul

Job for named-chroot.service failed because the control process exited with
error code. See "systemctl status named-chroot.service" and "journalctl -xe"
for details.



[root at ns1.frv.ma:/var/named/meganet]#systemctl status named-chroot.service
-l

● named-chroot.service - Berkeley Internet Name Domain (DNS)

   Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabled;
vendor preset: disabled)

   Active: failed (Result: exit-code) since Tue 2022-03-15 08:46:11 EDT;
6min ago

  Process: 3045 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" ==
"yes" ]; then /usr/sbin/named-checkconf -t /var/name     d/chroot -z
"$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi
(code=exited, status=1/FAILURE)



Mar 15 08:46:11 ns1.frv.ma systemd[1]: named-chroot.service: control process
exited, code=exited status=1

Mar 15 08:46:11 ns1.frv.ma systemd[1]: Failed to start Berkeley Internet
Name Domain (DNS).

Mar 15 08:46:11 ns1.frv.ma systemd[1]: Unit named-chroot.service entered
failed state.

Mar 15 08:46:11 ns1.frv.ma systemd[1]: named-chroot.service failed.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20220315/c187f581/attachment.htm>