- dns-wg - mailman.ripe.net

DNS-OARC 44 - Call for Contribution
by Petr Špaček 13 Sep '24

13 Sep '24

PLEASE NOTE THIS Call for Contribution is for OARC 44, February 2025. We are posting it before OARC 43 has taken place to give submitters plenty of time, but the OARC 43 programme is set and we hope to see you there. 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! Here’s a non-exhaustive list of ideas: - Operations: Any operational gotchas, lessons learned from an outage, details/reasons for a recent outage (how to improve time to recovery, tooling), interoperability concerns and experience. - Deployment: DNS config management and release process. - Monitoring: Log ingestion pipeline, analytics infrastructure, anomaly detection. - Scaling: Performance management and metrics. Server efficiency. - Security: DoS experience, attacks on the DNS, DNSSEC signing and validation. - Privacy: Encrypted transports, qname minimization, data anonymization. For further details please see https://www.dns-oarc.net/oarc44 Petr Špaček, for the DNS-OARC Programme Committee

1 0

DNS-WG at RIPE 89: Call for presentations
by Willem Toorop 12 Aug '24

12 Aug '24

Dear colleagues, Summer is at its peak, but RIPE 89 in Prague is approaching! The RIPE 89 meeting will be held from 28 October till 1 November 2024. Our working group meeting is currently scheduled on the 30th of October at 9:00am, 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 half September. Cheers, Willem on behalf of the RIPE DNS Working group co-chairs (Dodo, Moritz and me)

1 0

Sunsetting ns.ripe.net - new domain objects can no longer reference ns.ripe.net
by Paul de Weerd 18 Jun '24

18 Jun '24

Dear colleagues, On 6 June, we announced an updated schedule for the retirement of the "ns.ripe.net" secondary DNS service for LIRs. In this updated schedule, the first step was to stop accepting delegation requests with the name server "ns.ripe.net" in them. We have therefore adjusted our reverse DNS checking process to reject new delegation requests with "ns.ripe.net". If you are using this secondary service, you may also begin an orderly transition away from it, by updating the NS records in your zones, and then updating your domain objects in the RIPE Database, to remove "nserver" attributes containing "ns.ripe.net". Later this week, we will send out emails to users of the service, with a link to our RIPE Labs article, and instructions for stopping the use of this service. If you have any questions, please email dns(a)ripe.net. Regards, Paul de Weerd Manager Global Information Infrastructure team RIPE NCC

1 0

Retiring ns.ripe.net
by Paul de Weerd 06 Jun '24

06 Jun '24

Dear colleagues, We have published a RIPE Labs article on how we believe it is now time to retire the secondary DNS service for member’s reverse DNS delegations, ns.ripe.net: https://labs.ripe.net/author/anandb/retiring-nsripenet/ We are proposing to retire the secondary DNS service by the end of 2024 and we're asking for your input and feedback on this proposal. Please share any feedback on the DNS Working Group mailing list by 16 May 2024. Once we’ve collected your feedback, we will discuss this topic in the DNS Working Group session at RIPE 88 on Wednesday, 22 May 2024. Paul de Weerd Manager Global Information Infrastructure team RIPE NCC

10 12

DNS-OARC 43 - moved to Prague, CZ - 2024 October 26-27
by Petr Špaček 04 Jun '24

04 Jun '24

DNS-OARC 43 Workshop has moved to Europe and will be held right before RIPE 89. New location: Prague, Czech republic New date: 2024 October 26-27 (before RIPE 89) Details: https://www.dns-oarc.net/oarc43 Call for presentations is open until 2024-07-23 23:59 UTC You can also look forward to DNS Community day which will happen in the original location and date. See https://indico.dns-oarc.net/e/SMR2024 for more details. See you there! -- Petr Špaček, for the DNS-OARC Programme Committee

1 0

DELEG
by Andrew Campling 27 May '24

27 May '24

If Tale's DELEG update presentation at the RIPE 88 DNS wg session last week was of interest, you may also find our recent panel discussion on the same topic with Paul Mockapetris, Paul Vixie and Ralf Weber useful. If you missed it, the recording is at https://419.consulting/encrypted-dns/f/deleg-the-hairy-dns-camel. Andrew

1 0

Ars technica coverage of C-root's failure to refresh
by Willem Toorop 24 May '24

24 May '24

FYI: Ars technica published an article covering the recent C-root failure to refresh. See: https://arstechnica.com/security/2024/05/dns-glitch-that-threatened-interne…

1 0

Fwd: [ripe-list] DNS Resolver Recommendations Published (ripe-823)
by Shane Kerr 17 May '24

17 May '24

Dear RIPE DNS working group, Here is a belated notice that the DNS Resolver Recommendations document was published a couple of weeks ago. Apologies for not mentioning it sooner! Cheers, -- Shane

1 0

GOV zone operational update: DNSSEC transition to algorithm 13
by Christian Elmerot 13 May '24

13 May '24

Cloudflare will start the transition of the .GOV zone to use DNSSEC signing algorithm 13 (ECDSA P-256) about a week from now. We do not expect any action to be required by the operators of DNS resolvers or by end-users due to this change. This note is being sent as a courtesy, in the interests of operational transparency.. We plan to start the transition on May 20th, 2024. The initial step will be to include algorithm 13 signatures alongside algorithm 8 signatures in signed responses sent by the authoritative .GOV nameservers. The transition will proceed through the following sequence of events: 1. Algorithm 13 signatures are published in addition to algorithm 8 signatures 2. Algorithm 13 DNSKEY records are published alongside the current algorithm 8 DNSKEYs 3. Algorithm 13 DS record is published in the root zone 4. Algorithm 8 DS record is removed from the root zone 5. Algorithm 8 DNSKEY records are removed 6. Algorithm 8 signatures are removed from responses Cloudflare has been using algorithm 13 for zone signing since 2015, pioneering its use to the wider community. The widespread adoption since serves as a testament to the maturity of the resolver ecosystem's ability to recognize and validate the algorithm. Other important zones also use algorithm 13 today, such as the .COM and .NET Top-Level Domains (TLDs) that transitioned to algorithm 13 in the fourth quarter of 2023. While we anticipate minimal operational impact for end users, we encourage you to reach out to us with any questions or reports of unexpected behavior related to the transition. Christian Elmerot, Cloudflare

1 0

Survey & invitation: Open source quality assurance & risks @ RIPE 88 Open Source WG
by Petr Špaček 13 May '24

13 May '24

Dear DNS colleagues, I invite you to RIPE 88 Open Source WG discussion about Open source quality assurance & risks. To fuel the discussion please fill out a 5-minute survey here: https://ec.europa.eu/eusurvey/runner/RIPE88OpenSourceWGSurvey You opinions are very welcome even if you don't plan to attend the meeting! Our goal is to find out what people actually look for when assessing open source quality and risks associated with the software. During the RIPE 88 open source session we will have a speculative session where we will present survey results about how people see the open-source Q&A processes, compare these wishes with real example of what is being done today around BIND DNS server, and follow all that with an open discussion at the microphone. See you in Krakow! -- Petr Špaček Internet Systems Consortium

1 0