serverPKI issues TLSA RRs or challenge responses for letsencrypt by updating files, included by the master file. If only included files plus SOA serial are changed (remaining master file unchanged), then it may happen, that named stops signing and propagating zone file changes.
This is really a bind issue, up to bind-9.12.
It would be helpfull, if we could find a workaround for serverPKI to prevent from this bug.
serverPKI issues TLSA RRs or challenge responses for letsencrypt by updating files, included by the master file. If only included files plus SOA serial are changed (remaining master file unchanged), then it may happen, that named stops signing and propagating zone file changes. This is really a bind issue, up to bind-9.12.
It would be helpfull, if we could find a workaround for serverPKI to prevent from this bug.