Re: The root KSK roll has occurred
Well that explains the DNS weirdness I was seeing this morning. I had just made a significant network change and initially thought I screwed something up. After 10 minutes of halfhearted troubleshooting and poking around my configs I began to suspect DNS issues. Before I could do more digging, it magically resolved itself. -A On Thu, Oct 11, 2018 at 9:44 AM Selphie Keller wrote: > > Pretty awesome moment in history, confirmed my DNS resolvers are showing > 20326. Also, seeing the new key on public resolvers like cloudflare and > level3, google 8.8.8.8 and 8.8.4.4 still have 19036, likely cache. > > > > On Thu, 11 Oct 2018 at 10:07, Mehmet Akcin wrote: >> >> Congratulations for rolling the root zone KSK. >> >> On Thu, Oct 11, 2018 at 9:01 AM Matt Larson wrote: >>> >>> On behalf of the root zone management partners (ICANN and Verisign), I >>> would like to report that the root KSK rollover occurred at 1600 UTC today, >>> 11 October, with the publication of the root zone with serial number >>> 2018101100. >>> >>> For the 48 hours after the rollover, we will be monitoring several mailing >>> lists, including this one, so please reply here with any issues or concerns. >>> >>> Matt >>> -- >>> Matt Larson, VP of Research >>> ICANN Office of the CTO >>>
Re: The root KSK roll has occurred
I can also confirm that all of my internal DNS systems see the new key. I am very excited for the future of DNS especially with many public resolvers supporting DNSSEC and DNS over TLS. Bryce Wilson, AS202313 > On Oct 11, 2018, at 9:42 AM, Selphie Keller wrote: > > Pretty awesome moment in history, confirmed my DNS resolvers are showing > 20326. Also, seeing the new key on public resolvers like cloudflare and > level3, google 8.8.8.8 and 8.8.4.4 still have 19036, likely cache. > > > >> On Thu, 11 Oct 2018 at 10:07, Mehmet Akcin wrote: >> Congratulations for rolling the root zone KSK. >> >>> On Thu, Oct 11, 2018 at 9:01 AM Matt Larson wrote: >>> On behalf of the root zone management partners (ICANN and Verisign), I >>> would like to report that the root KSK rollover occurred at 1600 UTC today, >>> 11 October, with the publication of the root zone with serial number >>> 2018101100. >>> >>> For the 48 hours after the rollover, we will be monitoring several mailing >>> lists, including this one, so please reply here with any issues or concerns. >>> >>> Matt >>> -- >>> Matt Larson, VP of Research >>> ICANN Office of the CTO >>>
Re: The root KSK roll has occurred
Pretty awesome moment in history, confirmed my DNS resolvers are showing 20326. Also, seeing the new key on public resolvers like cloudflare and level3, google 8.8.8.8 and 8.8.4.4 still have 19036, likely cache. On Thu, 11 Oct 2018 at 10:07, Mehmet Akcin wrote: > Congratulations for rolling the root zone KSK. > > On Thu, Oct 11, 2018 at 9:01 AM Matt Larson wrote: > >> On behalf of the root zone management partners (ICANN and Verisign), I >> would like to report that the root KSK rollover occurred at 1600 UTC today, >> 11 October, with the publication of the root zone with serial number >> 2018101100. >> >> For the 48 hours after the rollover, we will be monitoring several >> mailing lists, including this one, so please reply here with any issues or >> concerns. >> >> Matt >> -- >> Matt Larson, VP of Research >> ICANN Office of the CTO >> >>
Re: The root KSK roll has occurred
Congratulations for rolling the root zone KSK. On Thu, Oct 11, 2018 at 9:01 AM Matt Larson wrote: > On behalf of the root zone management partners (ICANN and Verisign), I > would like to report that the root KSK rollover occurred at 1600 UTC today, > 11 October, with the publication of the root zone with serial number > 2018101100. > > For the 48 hours after the rollover, we will be monitoring several mailing > lists, including this one, so please reply here with any issues or concerns. > > Matt > -- > Matt Larson, VP of Research > ICANN Office of the CTO > >
