March 2026 - dns-wg - mailman.ripe.net

Co-chair selection: Collecting expressions of support now
by Moritz Müller 19 Mar '26

19 Mar '26

Dear colleagues, I am glad to announce that we have one candidate for the co-chair position that will become vacant at RIPE 92. We will now collect expressions of support (or opposition) from the mailing list until Monday, 18 May 2026, and will announce the results on Thursday, 21 May 2026 during the DNS working group session at the RIPE 92. Please also provide a short statement when expressing your support or opposition. Our candidate is: ***************************************** Name: Marc van der Wal Nominated by: self-nomination Statement by Marc: I would hereby like to nominate myself as a candidate for becoming a co-chair of the RIPE DNS working group. I’ve been working as an R&D engineer at Afnic for almost 4 years now, during which I’ve been involved with many different aspects of DNS operations: DNS testing tools such as Zonemaster or IBDNS, e-mail security with SPF, DKIM and DMARC, fighting abuse, and so on. As a regular RIPE attendee, I’ve been very happy with the way DNS working group sessions have been led during the past few years. I want to do more for the international community and, as a hypothetical co-chair, help keeping the high quality of those working group sessions. I am particularly sensitive to diversity, equality and inclusion as well. Although it would be a first experience in such a role, I am a fast learner, and I know I can count on input and support from fellow chairs, and from colleagues like Sandoche Balakrichenan who co-chaired the IoT working group. ***************************************** Best regards, Moritz, for the RIPE DNS working group co-chairs (Yevheniya, Ulrich and me)

3 2

DNS propagation inconsistencies across European resolvers — observations and data
by Vahid Shaik 09 Mar '26

09 Mar '26

Hi team, I've been investigating DNS propagation behavior across European resolvers and wanted to share some observations that might be useful to the group. When testing DNS record changes (particularly A, AAAA, and MX records) across resolvers in different RIPE member regions, I've noticed significant inconsistencies in how quickly changes propagate — even when TTLs are identical. Some examples: * Records with TTL 300 updated within 5 minutes on Cloudflare (1.1.1.1) and Google (8.8.8.8), but took 15-25 minutes on several ISP resolvers in DE, NL, and FR. * CNAME chains with 3+ levels caused noticeably slower propagation compared to direct A records, particularly on resolvers that don't support aggressive NSEC caching (RFC 8198). * Some ISP resolvers appear to enforce a minimum TTL floor (often 300-600s), overriding the authoritative server's lower TTL values. For anyone investigating similar behaviour, I've found it helpful to query the same record from multiple global locations simultaneously to identify which resolvers are lagging. We built a tool called DNS lookup<https://dnsrobot.net/dns-lookup> that does this at it queries from 20+ server locations in parallel and shows per-location results with response times. Has anyone else on the list observed ISP resolvers in the RIPE region enforcing minimum TTL values? RFC 8767 (Serving Stale Data) seems related, but I'm curious whether this is intentional policy or just aggressive caching implementations. Regards, Vahid

4 5

[RIPE 92] DNS WG: Call for presentations
by Yevheniya Nosyk 02 Mar '26

02 Mar '26

Dear colleagues, It might still seem far away, but RIPE 92 in Edinburgh is approaching. The RIPE 92 meeting will be held from 18th to 22nd May 2026. Our working group meeting is currently scheduled for 21st May at 11:00 am, but please note that this may still change. This e-mail is our first official call for topics for the DNS working group session. From RIPE 91 onwards, all plenary and working group proposals can be submitted through the same system, Pretalx. Please submit your proposals by 9 March 2026 using the following link: https://ripe92.ripe.net/present/call-for-presentations/. Alternatively, you may still send your proposals directly to us at <dns-wg-chairs AT ripe.net>. If using Pretalx, please pay special attention to the following fields: • Talk type: This field is not relevant to us. Select any option you like. Instead, make sure that you fill in the time you will need for your presentation, including Q&A, in the "Duration" field. • Track: Make sure that you select "DNS WG" • Duration: See "Talk type" above You can find more information on the Pretalx system here: https://ripe92.ripe.net/present/how-to-submit-a-proposal/ As usual, both in-person and remote participation in the working group is possible. We plan to send out the first round of notifications at the end of March 2026. Cheers, Yevheniya on behalf of the RIPE DNS Working Group co-chairs (Moritz, Ulrich and me) -- Yevheniya Nosyk, Ph.D. Cybersecurity Researcher https://korlabs.io

1 1