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] K-root DNS Service Incident
- Previous message (by thread): [dns-wg] Algorithm Upgrade for RIPE NCC DNS Zones
- Next message (by thread): [dns-wg] K-root DNS Service Incident
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Romeo Zwart
romeo.zwart at ripe.net
Mon Nov 30 12:03:44 CET 2015
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 URL below): https://atlas.ripe.net/dnsmon/group/k-root?dnsmon.session.color_range_pls=0-30-30-70-100&dnsmon.session.exclude-errors=true&dnsmon.type=server-probes&dnsmon.zone=k-root&dnsmon.startTime=1448835600&dnsmon.endTime=1448877600&dnsmon.ipVersion=both&dnsmon.server=193.0.14.129 After initial investigation, the RIPE NCC took counter-measures during the incident. The results of these measures are partially visible in DNSMON. The full effect of the mitigations implemented roughly coincided with the end of the event. We will investigate the events and the effectiveness of our response further and report about this in the near future. Kind regards, Romeo Zwart
- Previous message (by thread): [dns-wg] Algorithm Upgrade for RIPE NCC DNS Zones
- Next message (by thread): [dns-wg] K-root DNS Service Incident
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]