named service suddenly fails to start

[Reindl Harald]

Am 04.11.21 um 20:27 schrieb Bruce Johnson via bind-users:
> On Nov 4, 2021, at 12:01 PM, Bruce Johnson <johnson at pharmacy.arizona.edu 
> <mailto:johnson at pharmacy.arizona.edu>> 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>
> 
> named-checkconf -z revealed a name had been entered with underscores. 
> The person responsible has been sacked. (not really, merely reminded no 
> underscores are allowed in A records :-)
> 
> Does named-checkzone not check for this?

but what should it do at the point of a service restart?

the better question is why don't your admin backends prevent such mistakes