This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December
- Previous message (by thread): [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December
- Next message (by thread): [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jaap Akkerhuis
jaap at NLnetLabs.nl
Tue Dec 29 19:58:10 CET 2015
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. > > > > According a message from Stephane Bortzmeyer > > > > "The RIPE name server was retired on 16 december, for unknown > > reasons (as far as I know, the RIPE-NCC did not communicate on > > that)." > > > > Can you comment on that? > > With this limited amount of information, that would be hard. Which zones > are we talking about and what does 'retired' mean in this context? > > I haven't seen Stephane's message (yet). Was that a private message or > sent to a mailing list? Can you forward the whole message or have > Stephane provide more detail about his observations directly to me? > It seems that I have indeed removed to much of the context. 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 <https://www.ripe.net/ripe/mail/archives/dns-wg/2015-December/003184.html> that it had impacted RIPE's DNS service. Apparently Stephan wanted to know why RIPE NCC dropped serving the .tr zone. (My guess, since de RIPE NCC dropped out of the root zone as well, it was done in coordination with the tr people). So I was just curious wat happened on RIPE's end. jaap
- Previous message (by thread): [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December
- Next message (by thread): [dns-wg] RIPE NCC Authoritative and Secondary DNS services on Monday 14 December
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]