- dns-wg - mailman.ripe.net

DNS-WG at RIPE 90: Call for presentations
by Moritz Müller 31 Mar '25

31 Mar '25

Dear colleagues, It might still seem far way, but RIPE 90 in Lisbon is getting closer! The RIPE 90 meeting will be held from 12 until 16 May. As last time, our working group meeting is currently scheduled on Wednesday morning. More concrete 14 May at 9:00 am, but note that this may still change. This e-mail is our first official call for topics for the DNS working group session. If you are interested in presenting, please send your proposals to dns-wg-chairs(a)ripe.net. Please also indicate how much time you would need for your presentation including Q&A. As usual, both in-person and remote participation in the working group is possible. We plan to send out a first round of notifications beginning of April. Cheers, Moritz on behalf of the RIPE DNS Working group co-chairs (Dodo, Willem and me)

2 1

Call for nominations/volunteers to co-chair the RIPE DNS working group
by Doris Hauser 26 Mar '25

26 Mar '25

Dear Colleagues, This is a call for nominations or volunteers to co-chair the RIPE DNS working group. ************************************************************************************* Please DO NOT reply to this message if you wish to propose a volunteer. ************************************************************************************* Call for RIPE DNS Working Group Chair ------------------------------------------------------ In accordance with the chair selection process we announce that one of our co-chairs (Doris Hauser) is stepping down after the upcoming RIPE Meeting (RIPE 90, near Lisbon) for personal reasons and we would like to invite volunteers, or nominations for someone to become a co-chair of the DNS working group. Anyone may volunteer, and anyone may be nominated by someone else (we will check with the person for acceptance). To do this, please send a mail to <dns-wg-chairs AT ripe.net> before end of Thursday 23 April 2025 (UTC). Again, please DO NOT send your volunteer/nomination to the DNS WG mailing but rather the dns-wg-chairs mail alias. It would be helpful for candidates to give some words as to why they think they ought to be a co-chair, what new ideas, or improvements they might bring, and so on. We will publish the list of volunteers, along with anything the volunteers wish to include with their nomination, to this mailing list on Friday 24 April 2025. Discussion and support (or opposition) for each candidate can then be offered on the list. At the DNS working group session at RIPE 90, Moritz, Willem and Doris hope to announce consensus based on the mailing list discussion. Timeline ———— Wednesday, 26 March 2025 This call for volunteers posted to the dns-wg mail list Thursday, 23 April 2025 Deadline for volunteers/nominations Friday, 24 April 2025 List of candidates and call for support posted to the mail list Tuesday, 13 May 2025 Deadline for showing support for candidates/volunteers on the mail list Wednesday, 14 May 2025 DNS WG session at RIPE 90 References ---------- The RIPE working group chair job description is included in ripe-692: https://www.ripe.net/publications/docs/ripe-692 The DNS working group chair selection process is documented here: https://www.ripe.net/community/wg/active-wg/dns/dns-wg-chair-selection-proc… We have 3 co-chairs so the term is 3 years. The current approach was announced on this mailing list on 2018-07-17: https://www.ripe.net/ripe/mail/archives/dns-wg/2018-July/003566.html As always, please feel free to reach out to any of the chairs directly, to us as a group at dns-wg-chairs AT ripe.net, or discuss this or any other any relevant topic on this mailing list. Kind regards, Doris Hauser

1 0

CENTR Jamboree CfP
by Moritz Müller 13 Feb '25

13 Feb '25

Dear WG, On behalf of the CENTR PC, I’d like to share with you their call for proposals for their upcoming CENTR Jamboree in Lyon. --- From May 21st to 23rd, CENTR will host the CENTR Jamboree in Lyon. This event aims to bring together peers, experts, and leaders from various registries to exchange knowledge, discuss challenges, explore collaboration opportunities, and build professional networks across the European ccTLD industry. We invite both members and non-members to shape our agenda by submitting session proposals. Please see the attached call for proposals and consider contributing to this community event. Proposal submission deadline: March 28th Selection announcement: April 8th Looking forward to your proposals! --- Please get in touch with CENTR (secretariat(a)centr.org) in case of any questions. — Moritz

1 0

ICANN SSAC Survey on the anticipated impacts of open source regulation on the DNS infrastructure
by Maarten Aertsen 28 Jan '25

28 Jan '25

hello DNS wg, I ask for your help to inform policy makers of specific concerns in the DNS community. ICANN's Security and Stability Advisory Committee [1] is attempting to document the operational reliance on Free and Open Source Software (FOSS) in the Internet’s domain name infrastructure to inform policy discussions regarding the security of software and critical infrastructure. Our work aims aim to clear up misinformed assumptions by regulators and policy makers that may threaten the FOSS development and supply model, impacting operators of the Internet’s domain and routing systems. Please contribute your professional experience and opinion with a response to an anonymous qualitative survey: https://ec.europa.eu/eusurvey/runner/SSAC-open-source-software-in-DNS-and-r… Our report will be published on the ICANN website [2], with a target publication date in June. The survey will be closed for new submissions at the end of February anywhere on earth. Considering many of you use open source DNS implementations ever day, we ask you to help us make visible the scope and scale of FOSS in Internet infrastructure and share positive/negative impact of regulation you anticipate on the infrastructure you support. kind regards, Maarten [1] https://www.icann.org/en/ssac [2] https://www.icann.org/en/ssac/publications # What is SSAC? The Security and Stability Advisory Committee advises the ICANN community and ICANN Board on security and integrity matters related to Internet naming and address systems. We perform ongoing threat assessment and risk analysis to assess principal threats to stability and security of these systems. SSAC publications are available from https://www.icann.org/en/ssac/publications # What software are you looking at? Our focus is on recursive & authoritative nameservers, RDAP/WHOIS, EPP/registry and escrow functions. # Anonymous? We use the European Commission's EUsurvey tool, configured not to log IP addresses or other information with the potential to identify you. Your (anonymous) comments may be reprinted as entered in the report, if there is personally identifying information / personal data included in your comments, we will edit that from your remarks. -- Maarten Aertsen senior internet technologist, NLnet Labs

1 0

Don’t Miss the 44th DNS-OARC Workshop in Atlanta!
by Willem Toorop 24 Jan '25

24 Jan '25

Dear all, Join us for the 44th DNS-OARC Workshop in Atlanta, GA, USA, on February 6–7, 2025, right after NANOG 93 at the Atlanta Marriott Marquis (Location: https://maps.app.goo.gl/QLur9V7ahdgRJRgW8) *Workshop Highlights* Engaging sessions for operators, developers, and researchers: * Day 1: DNS resolver insights, authoritative operations, Encrypted Client Hello, and a Best Practices panel * Day 2: DNS abuse detection, tunneling analysis, DNSSEC innovations, and lightning talks Full Program schedule at: <https://www.dns-oarc.net/oarc44> *Register Now* Don’t miss out! Attend in person or remotely. Register here: <https://www.dns-oarc.net/oarc44> We look forward to seeing you at OARC 44! Best Regards, The DNS-OARC Programme Committee

1 0

Sunsetting ns.ripe.net - Final Cleanup - Wednesday, 15 January
by Anand Buddhdev 15 Jan '25

15 Jan '25

Dear colleagues, On Wednesday 15 January, we'll be moving on to the final phase of removing our secondary DNS service for LIRs (ns.ripe.net) and updating all associated objects in the RIPE Database. This update will remove the "nserver: ns.ripe.net" attribute from them. I am happy to report that 93% of the zones have been updated and stopped using ns.ripe.net as a secondary name server. The remaining zones that have not been updated will not be affected because they will have at least one working name server after this update. Therefore, we do not expect the DNS resolution of these zones to fail. The full sunsetting plan, published last year, is available on RIPE Labs: https://labs.ripe.net/author/anandb/retiring-nsripenet/ Regards, Anand Buddhdev

2 3

Re: [Ext] Reminder: New KSK Publication in DNS Root Zone
by Andres Pavez 07 Jan '25

07 Jan '25

Please note that there is a mistake with the time in my previous email. The new Key Signing Key (KSK) will be published in the DNS root zone on January 11 around 06:00 UTC, not 00:00 UTC as originally stated. Best regards, -- Andres Pavez Cryptographic Key Manager On 1/7/25, 11:39, "Andres Pavez" <andres.pavez(a)iana.org <mailto:andres.pavez@iana.org>> wrote: This is a reminder that the new Key Signing Key (KSK) will be published in the DNS root zone starting January 11 at 00:00:00 UTC. This will start the process of adoption of this trust anchor in RFC 5011 aware resolvers. We encourage operators to pay attention during this process to monitor for any unexpected consequences. Publishing the KSK is part of the process of ensuring widespread adoption of the KSK prior to its use in signing, currently scheduled for October 2026. For more details, please visit: https://www.iana.org/dnssec/files <https://www.iana.org/dnssec/files> Thanks, -- Andres Pavez Cryptographic Key Manager

1 0

Reminder: New KSK Publication in DNS Root Zone
by Andres Pavez 07 Jan '25

07 Jan '25

This is a reminder that the new Key Signing Key (KSK) will be published in the DNS root zone starting January 11 at 00:00:00 UTC. This will start the process of adoption of this trust anchor in RFC 5011 aware resolvers. We encourage operators to pay attention during this process to monitor for any unexpected consequences. Publishing the KSK is part of the process of ensuring widespread adoption of the KSK prior to its use in signing, currently scheduled for October 2026. For more details, please visit: https://www.iana.org/dnssec/files Thanks, -- Andres Pavez Cryptographic Key Manager

1 0

OARC 44 Call for Contribution deadline extension - Dec 9, 2024
by Willem Toorop 03 Dec '24

03 Dec '24

The deadline for OARC 44 abstract submission is extended to December 9, 2024, at 23:59 UTC. Thanks to those who already submitted, but we're still looking for more contributions. If you have something interesting to present and missed the chance last week, then this is your opportunity to still be part of the agenda for this event. This workshop will be a hybrid event. Date - 6-7 February 2025 Location - Atlanta Marriott Marquis - Atlanta, Georgia, USA Time zone - EST (UTC -5) Co-located with - NANOG 93 Deadline for Submissions - 2024-12-09 23:59 UTC All DNS-related subjects and discussion topics are welcome although we're particularly keen to hear about operational and security related experiences, best practices and practical advice; both for newcomers to the DNS arena and those who have been around for longer who want to learn more about new features and opportunities to improve resilience, security and privacy. If you have something interesting to share with the community that lies outside of the focus above, please don't be put off - if it's good, we'll be happy to include it. If you'd like to offer a talk, but are not quite sure what to pick, here's a non-exhaustive list of ideas: * *Operations*: Experiences, interoperability concerns, tooling tips, lessons learned from or details/reasons for a recent outage (how to improve time to recovery, tooling for detection/mitigation), operational 'gotchas'... * *Deployment*: DNS config management and release process. * *Monitoring*: Log ingestion pipeline, analytics infrastructure, anomaly detection. * *Scaling*: DNS performance management and metrics. Increasing DNS server efficiency. * *Security*: DoS experience, attacks on the DNS, DNSSEC signing and validation. * *Privacy*: Encrypted transports, qname minimization, data anonymization. * *Resilience*: Provisioning planning, load-balancing services, features (e.g. serve-stale) For further details please see https://www.dns-oarc.net/oarc44 Willem Toorop, for the DNS-OARC Programme Committee

1 0

Deadline Reminder: OARC 44 Call for Contribution - Dec 2, 2024
by Willem Toorop 29 Nov '24

29 Nov '24

The Programme Committee is seeking contributions from the community. This workshop will be a hybrid event. Date - 6-7 February 2025 Location - Atlanta Marriott Marquis - Atlanta, Georgia, USA Time zone - EST (UTC -5) Co-located with - NANOG 93 Deadline for Submissions - 2024-12-02 23:59 UTC All DNS-related subjects and discussion topics are welcome although we're particularly keen to hear about operational and security related experiences, best practices and practical advice; both for newcomers to the DNS arena and those who have been around for longer who want to learn more about new features and opportunities to improve resilience, security and privacy. If you have something interesting to share with the community that lies outside of the focus above, please don't be put off - if it's good, we'll be happy to include it. If you'd like to offer a talk, but are not quite sure what to pick, here's a non-exhaustive list of ideas: * *Operations*: Experiences, interoperability concerns, tooling tips, lessons learned from or details/reasons for a recent outage (how to improve time to recovery, tooling for detection/mitigation), operational 'gotchas'... * *Deployment*: DNS config management and release process. * *Monitoring*: Log ingestion pipeline, analytics infrastructure, anomaly detection. * *Scaling*: DNS performance management and metrics. Increasing DNS server efficiency. * *Security*: DoS experience, attacks on the DNS, DNSSEC signing and validation. * *Privacy*: Encrypted transports, qname minimization, data anonymization. * *Resilience*: Provisioning planning, load-balancing services, features (e.g. serve-stale) For further details please see https://www.dns-oarc.net/oarc44 Willem Toorop, for the DNS-OARC Programme Committee

1 0