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 almost always available.
Daniel
On 4/17/24 15:58, Anand Buddhdev wrote:
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 server and run the
knotc commands locally.
A different approach is to generate the remote knot.conf file from a template, using
something like Jinja with ansible or SaltStack. When the file changes, call "knotc
reload" to apply the changes.
Regards,
Anand
--
--
