On 4/9/25 02:29, Bagas Sanjaya wrote:
On Tue, Apr 08, 2025 at 07:38:44AM -0500, Matthijs Mekking wrote:
This time I was able to reproduce, thanks.
The reason why the key created by dnssec-keygen is retired because named
thinks it was in use already. When there is key timing metadata, the key
On Tue, Apr 08, 2025 at 07:38:44AM -0500, Matthijs Mekking wrote:
> This time I was able to reproduce, thanks.
>
> The reason why the key created by dnssec-keygen is retired because named
> thinks it was in use already. When there is key timing metadata, the key is
> considered to be in use (now o
On Mon, Apr 07, 2025 at 09:28:07AM -0500, Matthijs Mekking wrote:
> Hi,
>
> I have tried to reproduce but when I am issuing a rollover it selects the
> key I generate previously, as expected.
>
> If you believe this is a genuine bug, please support a bug report:
>
> https://gitlab.isc.org/isc-pr
This time I was able to reproduce, thanks.
The reason why the key created by dnssec-keygen is retired because named
thinks it was in use already. When there is key timing metadata, the key
is considered to be in use (now or in the past).
Only not previously used keys are considered as a succe
Hi,
I have tried to reproduce but when I am issuing a rollover it selects
the key I generate previously, as expected.
If you believe this is a genuine bug, please support a bug report:
https://gitlab.isc.org/isc-projects/bind9/-/issues/new?issuable_template=Default
and fill in the steps how
5 matches
Mail list logo
