1 Pro
2025
1 Pro
'25
12:34
One thing that came to my mind is to attach a strace to the running Knot
process, with a filter on open() syscall (and/or other file-manipulation
syscalls) and see what key- and backup-related files are being accessed
and how.
/Libor
On 01. 12. 25 12:31, Einar Bjarni Halldórsson via knot-dns-users wrote:
On 28 Nov
2025, at 15:09, Daniel Salzman via knot-dns-users <knot-dns-users(a)lists.nic.cz>
wrote:
Are you able to reproduce the issue with a different key set?
I have one domain on the staging signers waiting for KSK submission. It’s
completing an algorithm
rollover from RSASHA256 to ECDSAP256SHA256. Once I run `knotc zone-ksk-submitted` it
will trigger the error. Do you have ideas for things I can do before I trigger the error,
to collect more
and better data?
.einar
--