[dns-wg] K-root DNS Services Incident 1 December 2015

Dear colleagues, Between 05:10 and 06:10 UTC today, multiple root operators including K-root received an unusually large amount of query packets. We believe the event was similar to the events that took place yesterday, 30 November 2015. Following our investigation into this, we enabled counter me

Re: [dns-wg] K-root DNS Service Incident

Hi Romeo, On 30 November 2015 at 14:06:24, Romeo Zwart (romeo.zw...@ripe.net) wrote: Hi Nico,  On 15/11/30 13:36 , Nico CARTRON wrote:  >[…] >  > Thanks for the heads-up - would be interesting to know which  > countermeasures you implemented?  That will be part of the follow up message. To the a

Re: [dns-wg] K-root DNS Service Incident

Hi Nico, On 15/11/30 13:36 , Nico CARTRON wrote: > Hello Romeo, > > On 30 November 2015 at 12:05:03, Romeo Zwart (romeo.zw...@ripe.net > ) wrote: > >> Dear colleagues, >> >> Between about 07:00 and 09:15 UTC today multiple root operators >> including K-root were re

Re: [dns-wg] K-root DNS Service Incident

Hello Romeo, On 30 November 2015 at 12:05:03, Romeo Zwart (romeo.zw...@ripe.net) wrote: Dear colleagues,  Between about 07:00 and 09:15 UTC today multiple root operators  including K-root were receiving an unusually large amount of query  packets. This was impacting the overall performance of K-r

[dns-wg] K-root DNS Service Incident

Dear colleagues, Between about 07:00 and 09:15 UTC today multiple root operators including K-root were receiving an unusually large amount of query packets. This was impacting the overall performance of K-root DNS services, as can be seen for example in DNSMON (with apologies for the unpleasant UR