Hi Daniel and Jan,
Thank you for your suggestions and acknowledgements.
Regards,
Anand
On 21/07/2017 10:35, Daniel Salzman wrote:
> Hello Anand and Jan,
>
> You are right. This case cannot be handled easily. We will extend the
> zone-purge command
> to be able to purge a specific unknown zone
Hello Anand and Jan,
You are right. This case cannot be handled easily. We will extend the
zone-purge command
to be able to purge a specific unknown zone or all unknown zones from the
databases
(journal, timer, and kasp). Since Knot 2.5.0 it is easy because the databases
are common
for all zone
Hey,
I think your arguments make sense, Anand. I would just suggest
slightly different solution: Add control command that removes all
orphaned zones from the journal (knotc journal-gc). It will be more
practical as you wouldn't have to call it for each zone you have
removed. It will be idempotent
Hello Knot DNS developers,
I have an observation about newer versions of Knot which use the new
single LMDB-based journal.
Suppose I have 3 slave zones configured in my knot.conf. Let's call them
zone1, zone2 and zone3. Knot loads the zones from the master and writes
data into the journal. Now su
