Hi,
I support this too!
Bind packages have the same setup, which makes more sense to me.
Package bind9 contains nameserver.
Package bind9utils contains mutiple tools.
I use bind for DNSSEC signing and I would like to check the signed zone
with a different software (but I don't need knot running as a service)
dpkg -L bind9utils |grep dnssec-verify$
/usr/sbin/dnssec-verify
dpkg -L knot |grep kzonecheck$
/usr/bin/kzonecheck
cheers,
-arsen
On Tue, 19 Mar 2019 15:10:38 +0100 Daniel Baumann
<daniel.baum...@progress-linux.org> wrote:
Package: knot
Severity: wishlist
Hi,
I'm maintaining zone files in a git repository, which are then via ssh
trigger deployed to the knot master, which is a fairly convenient setup.
Now, in order to not accept syntax errors in zone files on the git
server in the first place (and thus both avoiding automatic deployment
to the knot server and have the "faulty" git commits not make it in the
repository at all).. it would be very nice if the kzonecheck utility
could be moved from knot to knot-dnsutils.
Currently, I would need to install knot on the git server just to get
kzonecheck which is not really a good idea.
Regards,
Daniel
