Hi Knot DNS developers,
I've seen the discussion about the breaking changes between LMDB 0.9 and
1.0.
I understand that Knot DNS 3.6 will have some magic in it to
automatically migrate the databases.
However, my concern is about the installation of LMDB itself. Currently,
our Knot DNS packages depend on the "lmdb-libs" package from the
distribution (RedHat and derivatives), and it is version 0.9.x. RedHat
is conservative, is unlikely to update to 1.0, because that would break
everything, so I expect the RedHat packages to remain at 0.9.
Will the new Knot DNS require newer LMDB, and if so, is it expected that
we'll have to roll our own packages for LMDB? Or do you intend to bundle
LMDB with Knot DNS as you do with some other libraries?
Regards,
Anand Buddhdev
RIPE NCC
Hi,
I do want to point out: http://www.lmdb.tech/doc/upgrading.html
tl;dr dump your databases *before* upgrading.
I got bitten by this on FreeBSD and had had to fall back to lmdb 0.93.5
Has anyone succeeded in this migration your knot databases to lmdb 1.0?
Which knot databases are involved? (journal, timers, kasp, …?)
Thanks and regards,
Michael
Hello
Each action I try to do on knot gets the error
error: failed to load configuration file '/usr/local/etc/knot/knot.conf'
(MDB_BAD_TXN: Transaction must abort, has a child, or is invalid)
What can I do ? (configuration not changed recently)
Hi
I have two questions about this blog post on multi-signers: https://en.blog.nic.cz/2025/05/07/knot-dns-in-a-complex-dnssec-topology/
First, the blog post shows auto-increment SOA serial mode for the zone files in-line with the docs example:
```
zonefile-sync: -1zonefile-load: difference-no-serial
journal-content: all
```
This would work fine for me in general, I don't mind zone files being the "source of truth".
But the docs has a note "This mode is not suitable if the zone can be modified externally (e.g. DDNS, knotc)."
Do I understand correctly that this is because any dynamic changes to the zone get wiped on reboot ? So, for example, if the only external DDNS modification in my environment is DNS-01 for cert issuance, it won't cause me a problem, because those are ephemeral by nature anyway ?
This then raises the second question, how would I deal with catlog zones with this concept of multi-signers ? Or are catlog zones too much trouble in a multi-signer environment ?
Thank you
