Thanks for providing the data.
So it looks to me that nothing has happened yet because you scheduled
the rollover at 2022112223 (November 22, 2022, 23:00:00 UTC). That's
why no successor has been created yet, the datetime is still in the future.
You can see in the state file that the key
> On Nov 21, 2022, at 3:29 AM, Matthijs Mekking wrote:
>
> Hi,
>
> It is hard to see what the problem is without any configuration or state
> information. Also, log level debug 3 gives you probably more useful logs when
> investigating a problem.
>
> Can you share (privately if you wish)
Hi,
It is hard to see what the problem is without any configuration or state
information. Also, log level debug 3 gives you probably more useful logs
when investigating a problem.
Can you share (privately if you wish) the key **state** files, and the
output of 'rndc dnssec -status' for the
Hello,
So I reconfigured one of my domains to use dnssec-policy. I’m using the policy
“default” + I’ve only added nsec3 stuff. All other timers / params are from
default. Working fine / as expected.
Luckily for me this is a domain that I don’t use much. So outages and mistakes
are easily
4 matches
Mail list logo
