WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
On Thu, 3 May 2012 09:07:42 +0200, Peter van Dijk wrote:
> Fixing this involves touching all DNSSEC-supporting modules and changing some interfaces.
> Therefor, we cannot do this for the 3.1 release.
> 3.1 will be released with a big warning about this specific setup; we intend to do a
> 3.1.1 (or similar) release sometime after that with a fix for this issue.
For now I can work around it by ensuring that the bind DNSSEC keys are
also present in the gsqlite3 backend database...