Good thought - I did run the `kzonecheck` utility on all forward and reverse zones, with no errors found in any.
I am not using DNSSEC internally, so ZONEMD should not be relevant. # kzonecheck -v /srv/knot/zones/master/144.168.192.in-addr.arpa debug: detected zone origin 144.168.192.in-addr.arpa. No error found # kzonecheck -vz /srv/knot/zones/master/lan.null-route.us debug: detected zone origin lan.null-route.us. No error found -- Ed V. --
