September 2022 - dns-wg - mailman.ripe.net

Call for RIPE DNS Working Group Chair (DO NOT REPLY)
by Shane Kerr 30 Sep '22

30 Sep '22

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 the term of one of our co-chairs (Shane Kerr) will soon expire 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. Note that having served two terms, in accordance with the selection process Shane is not eligible. To do this, please send a mail to <dns-wg-chairs(a)ripe.net> before Friday 7 October 2022. 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 Saturday 8 October 2022. Discussion and support (or opposition) for each candidate can then be offered on the list. At the DNS working group session at RIPE 85, Joao and Moritz hope to announce consensus based on the mailing list discussion. Timeline -------- Friday, 30 September This call for volunteers posted to the dns-wg mail list Friday, 7 October Deadline for volunteers Saturday, 8 October List of volunteers and call for support posted to the mail list Wednesday, 26 October Deadline for showing support for volunteers on the mail list Thursday, 27 October DNS WG session at RIPE 85 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/participate/ripe/wg/dns/dns-wg-chair-selection-process 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(a)ripe.net, or discuss this or any other any relevant topic on this mailing list. Cheers, -- Shane On behalf of the dns-wg chairs

1 0

DNS and K-root Quarterly Planning Q4 2022
by Paul de Weerd 27 Sep '22

27 Sep '22

Dear colleagues, The quarterly plans for our DNS Services, including K-root, can now be found at: https://www.ripe.net/support/documentation/quarterly-planning/dns-and-k-root For this quarter, we'll continue with our day-to-day operations and update the operating system of some of our DNS servers. We hope that by providing these plans, we can better inform the community of the ongoing developments on the DNS services we operate and get feedback on our work. If you have any input on these plans or suggestions for future work, please reach out to us. Kind regards, Paul de Weerd RIPE NCC

1 0

Panel discussion on learnings from deploying encrypted DNS at scale
by Andrew Campling 19 Sep '22

19 Sep '22

Participants on this list may be interested in catching up with a panel discussion that took place on my weekly call last Monday - the recording is accessible here<https://419.consulting/encrypted-dns/f/what-have-we-learned-so-far-part-2>. The discussion focused on learnings from the deployment and scaling of encrypted DNS resolvers with leading experts from across the industry. This is the second panel on this topic, building on the discussion that took place in May (here<https://419.consulting/encrypted-dns/f/what-have-we-learned-so-far-part-2>). The panel again featured senior people in the industry with significant DNS experience, namely: Joe Crowe from Comcast; Puneet Sood of Google; Otto Moerbeek of Open-Xchange; Paul Adair from Infoblox; Ralf Weber from Akamai. The discussion covered a range of issues, sharing both experiences from current deployments as well as giving an indication of forthcoming features in some of the leading DNS software. Andrew

1 0

New on RIPE Labs: Is It Possible for Encryption to Harm Cybersecurity?
by Alun Davies 19 Sep '22

19 Sep '22

Dear colleagues, Andrew Campling gives an update on developments in encrypted DNS and asks whether it’s possible that protocols intended to safeguard privacy might actually have a negative impact on cybersecurity for end users. Read more on RIPE Labs: https://labs.ripe.net/author/andrew_campling/is-it-possible-for-encryption-… Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Reminder: DNS-WG at RIPE 85: Call for presentations
by Moritz Muller 12 Sep '22

12 Sep '22

The summer break is probably over for most of us and it’s just a few more weeks until RIPE 85 in Belgrade. We kindly remind you to consider submitting a presentation to the DNS-WG session. If you have doubts whether a topic might suit the working group then please do not hesitate to contact us. Below you find the text of the original call for presentations. ########### Dear Colleagues, It’s summer time, but RIPE 85 in Belgrade is getting closer. As with last meeting in Berlin, this again will be a hybrid meeting. This e-mail is our official call for topics at the RIPE DNS working group session at the upcoming meeting. We're currently scheduled for 2022-10-27 (Thursday, 27 October 2022) at 11:00 CEST (09:00 UTC). Please send your presentation proposals, discussion topics to <dns-wg-chairs(a)ripe.net>. Of course, both in-person and remote participation in the working group is possible. Presentations, given at the DNS-OARC meeting the weekend before are welcome as well. ########## — Cheers, Moritz on behalf of the DNS-WG chairs

1 0

Extension: Deadline for OARC 39 abstract submission is extended to September 13, 23:59 UTC
by Hazel Smith 10 Sep '22

10 Sep '22

*Extension: Deadline for OARC 39 abstract submission is extended to September 13, 23:59 UTC * Please note: 1) We are looking for contributions and remote participation is actively supported. 2) OARC 39 will be a joint conference with CENTR and abstract submissions from CENTR members are welcome. Abstracts can be submitted using this link: https://indico.dns-oarc.net/event/44/abstracts/ Thanks, Hazel Smith, for the DNS-OARC Programme Committee Hazel Smith Site Reliability Engineer // Google Cloud, London hazelesque(a)google.com sre.google On Wed, Aug 31, 2022 at 8:53 PM Hazel Smith <hazelesque(a)google.com> wrote: > OARC 39 will be a two-day hybrid meeting held on 22 & 23 October in > Belgrade, Serbia at 10:00 AM (Local time - CEST (UTC+02:00)) The onsite > part of the meeting will be colocated with RIPE 85. > > The Programme Committee is seeking contributions from the community. > > All DNS-related subjects and suggestions for discussion topics are > welcome. For inspiration, we provide a non-exhaustive list of ideas: > > - Operations: Any operational gotchas, lessons learned from an outage, > details/reasons for a recent outage (how to improve TTR, tooling). > - 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/Privacy: DNSSEC signing and validation, key storage, > rollovers, qname minimization, DoH/DoT > > > *Note: OARC 39 will be a joint conference with CENTR and abstract > submissions from CENTR members are welcome.* > > As it is an hybrid workshop, we'd like to encourage brevity; presentations > should not be longer than 20 minutes (with additional time for questions). > > *Workshop Milestones:* > > 2022-07-30 Submissions open via Indico > 2022-09-06 Deadline for submission (23:59 UTC) > 2022-09-08 Preliminary list of contributions published > 2022-09-20 Full agenda published > 2022-10-03 Deadline for slideset submission and Rehearsal > 2022-10-22 OARC 39 Workshop - Day1 > 2022-10-23 OARC 39 Workshop - Day2 > > The Registration page and details for presentation submission are > published at: > <https://www.dns-oarc.net/oarc39> > > To allow the Programme Committee to make objective assessments of > submissions, so as to ensure the quality of the workshop, submissions > SHOULD include slides. Draft slides are acceptable on submission. > > Additional information for speakers of OARC 39 > > - Your talk will be broadcast live and recorded for future reference > - Your presentation slides will be available for delegates and others > to download and refer to, before, during and after the meeting > - *Remote speakers have mandatory rehearsal on 2022-10-04 at 14:00 > UTC.* It would be very useful to have your slides (even if draft) > ready for this. > > Note: DNS-OARC provides registration fee waivers for the workshop to > support those who are part of underrepresented groups to speak at and/or > attend DNS-OARC. More details will be provided when registration opens. > > If you have questions or concerns you can contact the Programme Committee: > https://www.dns-oarc.net/oarc/programme > via submissions(a)dns-oarc.net > > Hazel Smith, for the DNS-OARC Programme Committee > > OARC depends on sponsorship to fund its workshops and associated social > events. Please contact sponsor(a)dns-oarc.net if your organization is > interested in becoming a sponsor. > > (Please note that OARC is run on a non-profit basis, and is not in a > position to reimburse expenses or time for speakers at its meetings.) > > -- > > > Hazel Smith > > Site Reliability Engineer // Traffic Control SRE, London > > hazelesque(a)google.com > > sre.google >

1 0

Globalconnect NO DNS Cache
by André Pettersson 07 Sep '22

07 Sep '22

Hello, One of our customers is having issues with resolving a host name towards Globalconnect Norway DNS servers, that has not been updated after 48 hours, even though we have changed the hostname on our end and public DNS resolvers (Cloudflare, Google etc.) are returning correct data. If someone has contact with Globalconnect Norway or could point me in the right direction, please contact me off-list. Thank you. Kind regards, André Pettersson

1 0