Re: named service suddenly fails to start

2021-11-04 Thread Mark Andrews
> On 5 Nov 2021, at 07:11, Grant Taylor via bind-users > wrote: > > On 11/4/21 1:27 PM, Bruce Johnson via bind-users wrote: >> named-checkconf -z revealed a name had been entered with underscores. The >> person responsible has been sacked. (not really, merely reminded no >> underscores are

Re: named service suddenly fails to start

2021-11-04 Thread 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

Re: named service suddenly fails to start

2021-11-04 Thread Reindl Harald
Am 04.11.21 um 21:11 schrieb Grant Taylor via bind-users: On 11/4/21 1:27 PM, Bruce Johnson via bind-users wrote: 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

Re: named service suddenly fails to start

2021-11-04 Thread Grant Taylor via bind-users
On 11/4/21 1:27 PM, Bruce Johnson via bind-users wrote: 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 :-) You might want to apologize to them. Underscores are

Re: named service suddenly fails to start

2021-11-04 Thread John Thurston
On 11/4/2021 11:27 AM, Bruce Johnson via bind-users wrote: 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 :-) Sounds to me like you might want to incorporate

Re: named service suddenly fails to start

2021-11-04 Thread 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 > wrote: This morning our server started failing to reload or start. checking the status reveals not a lot of info: systemctl status named-chroot ●

Re: named service suddenly fails to start

2021-11-04 Thread Bruce Johnson via bind-users
On Nov 4, 2021, at 12:05 PM, Reindl Harald mailto:h.rei...@thelounge.net>> wrote: 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=exi this

Re: named service suddenly fails to start

2021-11-04 Thread Bruce Johnson via bind-users
On Nov 4, 2021, at 12:01 PM, Bruce Johnson mailto:john...@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)

Re: named service suddenly fails to start

2021-11-04 Thread Reindl Harald
Am 04.11.21 um 20:01 schrieb Bruce Johnson via bind-users: 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

named service suddenly fails to start

2021-11-04 Thread Bruce Johnson via bind-users
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: