On 1/29/21 5:00 AM, Santiago Ruano Rincón wrote:
> Could you try it please?
Hi,
Sorry for the delay. I had to find the time to recreate that situation.
Now it works quite nicely:
knot[27809]: error: [gedalya.com.] zone already configured, ignoring
knot[27809]: error: [gedalya.net.] zone
On Thu, 21 Jan 2021 13:28:58 +0800 Gedalya wrote:
> Hi Jan,
>
> For some reason I didn't get your message via email, but saw it when looking
> at the Debian bug.
A message sent to n...@bugs.debian.org is forwarded to the maintainer,
but not to the submitter. For a message to be forwarded to
Hi Jan,
For some reason I didn't get your message via email, but saw it when looking at
the Debian bug.
I see a fix for this in 3.0.4 (89c9a233). When that's packaged I'll try to
confirm that this is fixed.
Thank you!
We have tried to reproduce your issue but we were not able to crash the
daemon. Maybe some logs or details of your approach could help us.
Also, move this issue to 'https://gitlab.nic.cz/knot/knot-dns/-/issues'
would be good idea.
Thanks for your report
Sorry, forgot to include the backtrace. Attached.
(gdb) run
Starting program: /usr/sbin/knotd -c /etc/knot/knot.conf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffad0ee8700 (LWP 17295)]
[New Thread
Package: knot
Version: 3.0.2-2
When zones are defined twice, in a catalog zone and in the config, after adding
the unsigned zone files (gedalya.net and/or gedalya.com below) and restarting
knot, knot seems to start generating keys for, and signing the same zone twice,
in parallel, and
6 matches
Mail list logo
