Hi Daniel,
Thanks for your response. I read and re-read the docs, but they were
unclear on the design intent, so I appreciate the clarification.
I suppose I'll stick with the file configuration for now. I'd love to
learn more about use-cases for the database if anybody cares to share.
It seems like a powerful feature with the right automation.
Anyways, much appreciated.
Cheers,
Bill
On 3/29/25 12:50, Daniel Salzman wrote:
Hi Bill,
You can't mix a configuration database and a configuration file.
You can initialize a database with `knotc conf-init` or `knotc
conf-import`.
Then if you start knotd, the database will be used for reading and
persistent writing.
The configuration database format is a custom format using LMDB. It's
not intended to be accessed externally!
Daniel
On 3/29/25 19:56, Billiam Crashkopf wrote:
Hi all,
I'm running Knot 3.4.4 on FreeBSD 14.2, installed from the
distribution package repository.
I'm trying to understand, is there a way to configure knotd using
both the configuration file and the database? For example, can I use
the configuration file for directives like listen and template, then
use the configuration database for storing individual zone settings?
So far, it appears that knotd only uses one or the other.
Furthermore, there doesn't seem to be any command to explicitly load
or flush configuration from the database. If I start with the config
file, I can initialize the database, but upon stopping knotd nothing
seems to be saved to the database. I also don't see any
documentation on tooling to inspect the database on disk. What is
the file format of the database?
If anybody can help me to know more about how it works I would be
most appreciative.
Thanks,
Bill
--
