- dns-wg - mailman.ripe.net

OARC 38 Call for Contributions
by Hazel Smith 03 May '22

03 May '22

OARC 38 will be a two-day hybrid meeting held on July 30th and 31st, 2022 starting at 10 am (Eastern)*. *The onsite part of the meeting will be co-located with IETF 114 (Philadelphia). 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 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-05-01 Submissions open via Indico 2022-06-20 Deadline for submission (23:59 UTC) 2022-06-21 Initial Contribution list published 2022-06-28 Full agenda published 2022-07-12 Deadline for slideset submission and Rehearsal 2022-07-30 OARC 38 Workshop - Day 1 2022-07-31 OARC 38 Workshop - Day 2 The Registration page and details for presentation submission are published at: https://www.dns-oarc.net/oarc38 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 38: * 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-07-12 at 15: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 // Google Cloud, London hazelesque(a)google.com sre.google

1 0

Changes to Time-to-Live (TTL) values in reverse DNS zones
by Anand Buddhdev 22 Apr '22

22 Apr '22

Dear colleagues, In 2021, we announced a plan to change the time-to-live (TTL) values in the reverse DNS zones that we maintain. You may view the announcement here: https://www.ripe.net/ripe/mail/archives/dns-wg/2021-November/003928.html Many members of the community expressed support for our proposal. Therefore, we are going to make these changes next week on Wednesday 20 April. We will lower the TTL of NS records to 86400 (1 day) and that of DS records to 3600 (1 hour). Note that the TTL of records imported from other Regional Internet Registries (RIRs) will not be affected. Those records will be imported with the TTLs as published by the origin RIR. Regards, Anand Buddhdev RIPE NCC

5 9

New on RIPE Labs: Detecting DNS Root Manipulation
by Alun Davies 19 Apr '22

19 Apr '22

Dear colleagues, In 2021, when reports emerged that hosts in Mexico were unable to reach whatsapp.net, it was determined that middleboxes were to blame. These devices were intercepting the queries to the root instance hosted in China and sending a bogus reply. Taking this as their starting point, Qasim Lone and colleagues have been investigating the prevalence of middleboxes using RIPE Atlas: https://labs.ripe.net/author/qasim-lone/detecting-dns-root-manipulation/ Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

DNS4EU
by Andrew Campling 19 Apr '22

19 Apr '22

Tomorrow is the revised deadline for responses to the European Commission's DNS4EU Call for Proposals. I don't have the impression that there will be a large number of responses from the industry, does anyone have a different perspective? Andrew

1 0

.arpa ns changes
by James Mitchell 15 Apr '22

15 Apr '22

Dear network operators and other interested parties: This is advance notice that beginning 25 April, the hostnames for the nameservers for the .ARPA zone are planned to change. The new names will correspond to the same IP addresses that already provide the service. This change is planned occur in two phases. On Monday, April 25, the A, C, and E nameservers will change to their new hostnames. The remaining nameservers will change one week later on Monday, May 2. We do not expect any issues to arise from these changes. The work is being done as described in RFC 9120, in coordination with our root zone management partner Verisign and the IAB. Kind regards, James Mitchell Internet Assigned Numbers Authority

1 0

DNS and K-root Quarterly Planning Q2 2022
by Paul de Weerd 31 Mar '22

31 Mar '22

Dear colleagues, We've prepared our quarterly plans for our DNS services, including K-root. Please find them at https://www.ripe.net/support/documentation/quarterly-planning/dns-and-k-root We hope that by providing these plans, we can better inform the community of the ongoing work 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

Survey on DNS resolver operations and DNSSEC
by Moritz Müller 21 Mar '22

21 Mar '22

*co-chair hat off* Hi everyone, The DNS Security Extensions (DNSSEC) add integrity and authenticity to the Domain Name System (DNS). Now, more than 17 years after their standardization, we would like to hear from DNS recursive resolver operators about their experience with DNSSEC. For this reason, we have set up a short survey. It’s directed mainly towards organisations that run a recursive resolver. Filling out the survey should take roughly 5 to 10 minutes. https://forms.gle/FxTD9FofaogdvLqcA (link directs to Google Forms) This survey is carried out by SIDN Labs (https://sidnlabs.nl) and by the Swedish Internet Foundation (https://internetstiftelsen.se/en/). You can contact us via email: moritz.muller(a)sidn.nl Please excuse us, if you have received this email via different mailing lists. — Moritz Müller Research Engineer at SIDN Labs

1 0

Last call and final reminder for nominations to the 2022 Rob Blokzijl Award
by Carsten Schiefner 14 Mar '22

14 Mar '22

[Apologies for cross-posting to various RIPE lists] Dear DNS WG members - this is the last call and final reminder for nominations to the 2022 Rob Blokzijl Award that will be accepted until this Friday, 18th March, at 23:59 UTC. In seeking nominations for this prestigious award, which was created to celebrate Rob's contributions to the development of the Internet, the Award Committee (https://rob-blokzijl-foundation.org/2021/11/22/2022-award-committee/) is interested to receive nominations of those who have reflected Rob's approach in either a technical or operational capacity. Please give some consideration to nominating individuals - but also teams and groups of people! - in your own community and/or the wider industry in the RIPE region who, in your opinion, deserve to be recognised for their work to make the internet and/or internet community better. To specifically have this emphasised again after some according queries: nominations of teams and groups of people are very well possible and wished for as well in case their collective work would match the criteria of the call as laid out! The Award Committee is particularly interested to receive nominations of contributors who, in addition to their own contributions, have also supported and enabled others anywhere in the world. Also, the Award Committee would like to encourage those making nominations to consider not only the community members in the later stages of their careers or who are widely known but also those who may have contributed greatly in the springtime of their career or discreetly for the greater good or who may be considered to be part of an unrepresented group. And last but not least: those of you who previously have made a nomination other than Wilfried Woeber, the 2018 awardee, may want to consider resubmitting a nomination. The complete details of the call and the nomination process can be found at: https://rob-blokzijl-foundation.org/2021/11/25/call-for-nominations-2022/ Best wishes and kind regards Carsten (on behalf of the Award Committee)

1 0

RIPE DNS working group: Call for topics for RIPE 84
by Shane Kerr 07 Mar '22

07 Mar '22

Dear Colleagues, RIPE 84 is fast approaching. This is especially exciting because at least part of the community will be able to meet in person in Berlin. 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-05-19 (Thursday, 19 May 2022) at 11:00 CEST (09:00 UTC). Please send your presentation proposals, discussion topics, or anything you think that will be informative, important, and/or interesting for DNS fans in the RIPE community to <dns-wg-chairs(a)ripe.net>. As this is a hybrid meeting, both in-person and remote participation in the working group is possible. Cheers, -- Shane

1 0

follow up of "Update RIPE's DNS Zonemaster"
by Nick Cao 22 Feb '22

22 Feb '22

When doing a DNSSEC algorithm rollover from ecdsap256sha256 to ed25519 today, I got the error 'Unknown cryptographic algorithm' when updating ds-rdata field. A quick google search led me to https://www.ripe.net/ripe/mail/archives/dns-wg/2021-January/003796.html, which dates back to more than a year ago. It seems that the zonemaster deployment has not been updated to day, thus I would like to ask about the current progress.

5 7