> On 17 Apr 2024, at 14:12, Daniel Salzman via knot-dns-users
> wrote:
>
> Yes. You can forward the control socket using ssh (e.g. ssh -f -N -L
> /tmp/knot.sock:/run/knot/knot.sock -o 'StreamLocalBindUnlink=yes' server) and
> use knotc locally (knotc -s /tmp/knot.sock).
>
>
> On 4/17/24 15:
Hello!
If knotc reload works, restart isn't needed :-)
Reload for the zone set reconfiguration is okay. Restart is necessary mostly
for socket or worker reconfiguration
when knotd needs extra privileges. In the documentation there is a comment for
such configuration items.
Daniel
On 4/17/24
Hello,
When doing something quite dramatic in knot.conf like adding and/or removing a
zone, is "knotc reload" a suitable approach to honour those changes or would
you recommend restarting the whole process?
"knotc reload" seems to work just fine in test, I'm just looking for some
further c
Yes. You can forward the control socket using ssh (e.g. ssh -f -N -L
/tmp/knot.sock:/run/knot/knot.sock -o 'StreamLocalBindUnlink=yes' server) and
use knotc locally (knotc -s /tmp/knot.sock).
I don't think that native remote control support is worth implementation and
configuration when ssh is
On 17/04/2024 15:33, Einar Bjarni Halldórsson via knot-dns-users wrote:
Hi Einar,
[snip]
Is there a good way to remotely add zones to a knot secondary?
You could use socket plumbing tools such as netcat or socat to connect a
local socket to a remote one. Alternatively, just ssh into the ser
Hi,
I have a use case, where today we’re running BIND and a daemon uses rndc to
create/remove/update zones on secondary servers.
According to `man knotc` knotc only supports UNIX sockets (old ubuntu man page
showed ‘-p’ parameter to specify port).
I know I could use a catalog zone, but that wou
