On 17 Apr 2024, at 14:12, Daniel Salzman via
knot-dns-users <knot-dns-users(a)lists.nic.cz> 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:58, Anand Buddhdev wrote:
> 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.
>
Thanks Daniel and Anand!
SSH it is.
.einar