[dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

Dear colleagues, Yesterday, Monday 14 December 2015, RIPE NCC Authoritative DNS services were functioning in a severely degraded state during parts of the day. This was due to an attack on one of the ccTLDs for which the NCC hosts a secondary DNS service. The attack traffic started around 08:00 U

Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

On 15 Dec 2015, at 18:25, Brett Carr wrote: > > Thanks for the information Romeo I wonder if perhaps you would consider doing > a presentation at the next WG meeting on the issues you encountered and > mitigation techniques you used. > > Thanks > > Brett > +1 Cheers, -- Nico

Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

Thanks for the information Romeo I wonder if perhaps you would consider doing a presentation at the next WG meeting on the issues you encountered and mitigation techniques you used. Thanks Brett -- Brett Carr Senior DNS Engineer Nominet UK > On 15 Dec 2015, at 12:35, Romeo Zwart wrote: > >

Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

Hi Brett, On 15/12/15 18:25 , Brett Carr wrote: > Thanks for the information Romeo I wonder if perhaps you would consider doing > a presentation at the next WG meeting on the issues you encountered and > mitigation techniques you used. We will consider it. As you will understand, and will have

Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

Same question as for the root incident - would you be willing to share more information OTR with software implementors (such as well, me)? Pinky swear that I'm not the perpetrator. Best, Marek On 15 December 2015 at 18:48, Romeo Zwart wrote: > Hi Brett, > > On 15/12/15 18:25 , Brett Carr wrote:

Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

S Working Group > Subject: Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on > Monday 14 December > > Hi Brett, > > On 15/12/15 18:25 , Brett Carr wrote: > > Thanks for the information Romeo I wonder if perhaps you would consider > doing a presentation at the nex

Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

Romeo Zwart writes: > Yesterday, Monday 14 December 2015, RIPE NCC Authoritative DNS services > were functioning in a severely degraded state during parts of the day. > > etc. According a message from Stephane Bortzmeyer "The RIPE name server was retired on 16 december, for unknown

Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

Hi Jaap, On 15/12/29 13:08 , Jaap Akkerhuis wrote: > Romeo Zwart writes: > > > Yesterday, Monday 14 December 2015, RIPE NCC Authoritative DNS services > > were functioning in a severely degraded state during parts of the day. > > > > etc. > > According a message from Stephane Bortzmeyer >

Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

Romeo Zwart writes: > Hi Jaap, > > On 15/12/29 13:08 , Jaap Akkerhuis wrote: > > Romeo Zwart writes: > > > > > Yesterday, Monday 14 December 2015, RIPE NCC Authoritative DNS services > > > were functioning in a severely degraded state during parts of the day. > > > > > > etc. >

Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

Hi Jaap, > On 29 dec. 2015, at 19:58, Jaap Akkerhuis wrote: > > Romeo Zwart writes: > >> Hi Jaap, >> >>> On 15/12/29 13:08 , Jaap Akkerhuis wrote: >>> Romeo Zwart writes: >>> Yesterday, Monday 14 December 2015, RIPE NCC Authoritative DNS services were functioning in a severely degra

Re: [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December

Dear Jaap and colleagues, On 29 December you wrote to the list: > Stephane's message was on the centr security list which archives > seem to be sealed (contrary to what I thought). It was refering to > the attack on the .tr name servers about which you reported in >