Re: named service suddenly fails to start

Check-names in enforced by UPDATE independent of the format the zone is stored in.  Named-compilezone will also reject by default.   -k mode  This  option  performs  check-names  checks  with  the  specified  failure  mode.   Possible  modes are fail (the default for named-compilezo

Re: named service suddenly fails to start

I am not 100% sure, but what format of the zone were used? I think this should be usually catched by default check-names value on master zones. However, in masterfile-format, I found this sentence [1]: > In particular, *check-names* checks do not apply for the |raw| format. Does that mean dynami

Re: named service suddenly fails to start

> 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 a

Re: named service suddenly fails to start

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 N

Re: named service suddenly fails to start

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 records

Re: named service suddenly fails to start

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 l

Re: named service suddenly fails to start

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 so

Re: named service suddenly fails to start

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 ● named

Re: named service suddenly fails to start

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 nons

Re: named service suddenly fails to start

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) Loaded:

Re: named service suddenly fails to start

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 (/usr/lib/systemd

Re: named-service-stopped

Am 15.12.19 um 09:44 schrieb MEjaz: > We are an ISP, All of sudden during the midnight our named service was > down, please find the below snippet of the logs  when we checked the > logs  of “dmesg” and “/var/log/messages” > > Our bind name version is =  BIND 9.12.3-P1 > Is that advisable to

Re: named-service-stopped

On 15/12/2019 09:44, MEjaz wrote: > Our bind name version is = BIND 9.12.3-P1 > Is that advisable to upgrade our bind from the above version to the latest > stable one I can't comment on the cause of the failure, but 9.12 isn't supported any more. You should run the latest stable version, whi

RE: Named Service

Okay, if that doesn’t work, then temporarily until I can get the service figured out I will just do - adding "/usr/local/sbin/named" to /etc/rc.local From: Peter DeVries Sent: Tuesday, January 22, 2019 11:38 AM To: Jordan Tinsley Cc: bind-users Subject: Re: Named Service

Re: Named Service

*Sent:* Tuesday, January 22, 2019 11:32 AM > *To:* Jordan Tinsley > *Cc:* bind-users > *Subject:* Re: Named Service > > > > You didn't mention your OS. I'm assuming Redhat Linux. The files you > are looking for are /usr/lib/systemd/system/named{-chroot}.servi

RE: Named Service

Thank you for the information! Also, do I need to use the {-chroot} portion? Thanks, Jordan From: Peter DeVries Sent: Tuesday, January 22, 2019 11:32 AM To: Jordan Tinsley Cc: bind-users Subject: Re: Named Service You didn't mention your OS. I'm assuming Redhat Li

Re: Named Service

You didn't mention your OS. I'm assuming Redhat Linux. The files you are looking for are /usr/lib/systemd/system/named{-chroot}.service. The files are not included in the BIND source. The easiest thing is to pull them out of one of the existing redhat BIND packages and edit for your needs. Th

Re: Named Service

On 1/22/19 10:12 AM, Jordan Tinsley wrote: > Just wondering how to get the named service setup when compiling from > source? I'm kinda old school, but adding "/usr/local/sbin/named" to /etc/rc.local has always worked for me. AlanC ___ Please visit http

Re: Named Service

On 01/22/2019 08:12 AM, Jordan Tinsley wrote: I get an error that named.service doesn’t exist.  I may be overlooking documentation somewhere, but I don’t see anything about this. I don't think that the BIND source code includes distro / init daemon specific scripts / files. It's going to be u