Re: why did it take 26 hours for DSState to change to omnipresent?

2022-05-16 Thread Nick Tait via bind-users
On 16/05/22 21:34, Matthijs Mekking wrote: Hi Nik, On 16-05-2022 07:49, Nick Tait via bind-users wrote: Hi there. Ever since I updated my BIND configuration to use the new dnssec-policy feature (a year or so ago) my KSK/CSK rollovers have been a complete shambles. My problems stem from the

Re: why did it take 26 hours for DSState to change to omnipresent?

2022-05-16 Thread Matthijs Mekking
Hi Nik, On 16-05-2022 07:49, Nick Tait via bind-users wrote: Hi there. Ever since I updated my BIND configuration to use the new dnssec-policy feature (a year or so ago) my KSK/CSK rollovers have been a complete shambles. My problems stem from the inference (based documentation and

why did it take 26 hours for DSState to change to omnipresent?

2022-05-15 Thread Nick Tait via bind-users
Hi there. Ever since I updated my BIND configuration to use the new dnssec-policy feature (a year or so ago) my KSK/CSK rollovers have been a complete shambles. My problems stem from the inference (based documentation and examples) that running "rndc dnssec -checkds published" tells BIND that