named service suddenly fails to start

[Fred Morris]

Grant Taylor's reply is good, but you might also look at the check-names 
option. As he says, underscores are frowned on in hostnames but that's 
about it in theory if not in practice.

You could also contemplate changing the logging destination and level... 
or not.

--

Fred Morris

On Thu, 4 Nov 2021, Bruce  Johnson via bind-users wrote:
> 
> This morning our server started failing to reload or start.
>
> checking the status reveals not a lot of info:
>
> systemctl status named-chroot
> ● 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 Thu 2021-11-04 11:55:17 MST; 27s ago
>  Process: 2020 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -t /var/named/chroot -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exit>