BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
CALSCALE:GREGORIAN
PRODID:-//WordPress - MECv7.28.0//EN
X-ORIGINAL-URL:https://osmc.de/
X-WR-CALNAME:OSMC
X-WR-CALDESC:Open Source Monitoring Conference
X-WR-TIMEZONE:Europe/Berlin
BEGIN:VTIMEZONE
TZID:Europe/Berlin
X-LIC-LOCATION:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:20260329T030000
RRULE:FREQ=YEARLY;BYMONTH=03;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:20261025T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=4SU
END:STANDARD
END:VTIMEZONE
REFRESH-INTERVAL;VALUE=DURATION:PT1H
X-PUBLISHED-TTL:PT1H
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
CLASS:PUBLIC
UID:MEC-768d084123cb2ed6e871ad2019d3ae8a@osmc.de
DTSTART;TZID=Europe/Berlin:20261118T080000
DTEND;TZID=Europe/Berlin:20261119T180000
DTSTAMP:20260616T120855Z
CREATED:20260616
LAST-MODIFIED:20260616
PRIORITY:5
SEQUENCE:1
TRANSP:OPAQUE
SUMMARY:Monitoring DNSSEC
DESCRIPTION:The incident that occurred with the ccTLD “.de” on May 5th, 2026 brought a problem to the attention of a broad public that people more deeply involved in DNS and DNSSEC already knew: It is a well-known fact that DNS is a crucial resource for everything that uses the Internet, and, almost unnoticed by many, this is the case for DNSSEC as well. But while DNS usually fails in a containable way, a DNSSEC failure at the wrong place – such as in a ccTLD – can quickly wipe out a large part of the domains in a country, or even worldwide. It should be obvious that getting rid of DNSSEC is not the solution. One solution – or at least part of the solution is, not surprising for a talk at OSMC, monitoring DNSSEC. This talk provides a short introduction into DNSSEC, a summary of what can (and did) go wrong, and demonstrate a plugin that can be used to monitor many aspects of DNSSEC to make sure that at least some of the issues will be noticed – ideally before it’s too late.\n
URL:https://osmc.de/talks/monitoring-dnssec/
END:VEVENT
END:VCALENDAR