Re: Twice load - rndc.key ?
On Mon, 11 Jul 2022 21:01:48 +0200
Maurizio Caloro <maurizio@caloro.ch> wrote:
> why this will load the rndc.key twice ?
The log snippet below doesn't say it is loading the key twice. It
indicates that it attempting to configure two separate command
channels.
>
> # cat /lib/systemd/system/named.service
>
> [Service]
> EnvironmentFile=-/etc/default/named
> ExecStart=/usr/sbin/named -f $OPTIONS
> # ExecReload=/usr/sbin/rndc reload
> # ExecStop=/usr/sbin/rndc stop
First mistake: you should not be editing files in /lib/systemd/.
Instead copy the file to edit into /etc/systemd/, and edit it there. I
believe there is a systemd command that will do that for you if
necessary. The reason is that when an upgrade comes along, it will
stomp on any changes you have made in /lib/systemd/.
>
> --
>
> Jul 11 20:56:47 Star named[3129]: *configuring command channel from
> '/etc/bind/rndc.key'*
> Jul 11 20:56:47 Star named[3129]: command channel listening on
> 127.0.0.1#953 Jul 11 20:56:47 Star named[3129]: *configuring command
> channel from '/etc/bind/rndc.key'*
> Jul 11 20:56:47 Star named[3129]: couldn't add command channel
> ::1#953: address not available
>
It looks like it is successfully configuring its command channel on
IPv4 (127.0.0.1#953), and unsuccessfully on IPv6 (::1#953). If you
don't care about IPv6, you can probably ignore that.
I don't see all of those messages on my bind9 installation's log. I am
running bind9 1:9.16.27-1~deb11u1
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Reply to: