- dns-wg - mailman.ripe.net

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

OARC 46 Call for Contribution
by Ulrich Wisser 21 Feb '26

21 Feb '26

Apologies for cross posting! The next DNS-OARC meeting will be in Edinburgh immediately before Ripe 92. Please consider participating and maybe even submit a talk. Kind regards /Ulrich This workshop will be a hybrid event. Date - 16-17 May 2026 Location - Edinburgh, Scotland Times - approximately 09:00-16:00 UTC (Local time BST is UTC +1 ) Adjacent to - RIPE 92 (18 - 22 May 2026, https://ripe92.ripe.net/) Deadline for Submissions - 2026-03-06 23:59 UTC https://indico.dns-oarc.net/event/56/abstracts/ All DNS-related subjects and discussion topics are welcome although we're particularly keen to hear more 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. (These topics we think will complement the usual high-quality data-based research submissions we always hope to receive!) 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: 1. Operations & Deployment · Configuration management, deployment processes, and interoperability experiences. · Tools, tips, and making effective use of DNS software features. 2. Performance, Resilience & Scaling · Provisioning, load-balancing, and planning for resilience. · DNS performance management, efficiency improvements, and metrics. · Monitoring infrastructure: log pipelines, analytics, and anomaly detection. 3. Security, Privacy & Policy · DoS attacks, DNS abuse, DNSSEC signing and validation. · Privacy considerations, for example: encrypted transport, qname minimization, data anonymization. · Relevant global and regional policies, legislation, and compliance. 4. Research & Innovation · Data-driven testing, measurement, and analysis. · New protocols, protocol extensions, and next-generation namespace management. 5. Lessons & Learnings · Outage experiences, recovery stories, and cautionary tales For further details please see https://www.dns-oarc.net/oarc46 ..., for the DNS-OARC Programme Committee

1 0

ENUM (e164.arpa): background, scope, and coordination steps
by Hisham Ibrahim 18 Feb '26

18 Feb '26

Dear colleagues, This message summarises recent discussion regarding ENUM (e164.arpa) and clarifies the scope and next steps. The RIPE NCC has operated the e164.arpa registry for many years under instructions and coordination arrangements established with the ITU-T and IAB. These arrangements, and the operational context for how the registry is run, are described here: https://www.ripe.net/manage-ips-and-asns/dns/enum/iab-instructions/ Recently, a request was raised in the RIPE Database Working Group to support ENUM (e164.arpa) in RDAP for querying the RIPE Database. We noted that RDAP support for ENUM is not currently implemented, but could be added if there is clear interest. We also checked current query patterns and found a few hundred ENUM-related queries per day in DNS and in Database; so low usage, but not zero. Following discussion on the Database WG mailing list, including replies in support, we proposed implementing RDAP support for ENUM. While this is a limited operational change, it was recognised that anything touching E.164 and e164.arpa can raise political questions that go beyond the purely technical. As e164.arpa is directly linked to the ITU E.164 numbering system, the relevant points of contact are typically national administrations and the entities they designate. This led us to consult ITU-T Study Group 2 to clarify the status of ENUM and its usage and needs for ongoing support. ITU-T will ask member states for their feedback and share this with us. ITU-T provides an established and coordinated channel to reach those administrations, and importantly confirm whether any delegating authorities still rely on the service, so our technical decisions are informed by real-world use and help us avoid unnecessary operational risk, confusion, or compliance headaches (including in the context of regulatory frameworks such as NIS2). We are also reaching out to the IAB regarding these operations, which the RIPE NCC performs under its instruction on behalf of the global DNS and Internet community. I am sharing this message with the DNS, Database, Cooperation and RIPE NCC Services Working Group mailing lists to ensure all relevant working groups are informed. If you wish to share thoughts in response, please reply to the thread on the RIPE NCC Services WG mailing list. Best regards, Hisham Ibrahim Chief Community Officer, RIPE NCC

3 3

Re: Launch of The Internet Ecosystem Book
by Peter Anderson 09 Feb '26

09 Feb '26

*(Apologies for cross-posting)* As a researcher, I have never come across a highly intensive and inclusive book like "The Internet Ecosystem". The book englobes the whole Internet Ecosystem with the correct information compared to misleading information from blogs/wikipedia on the Internet. This book was reviewed by Vint Cerf. I have just completed the reading, I will highly recommend it and it is nice to have a copy to keep for reference. Professor Peter Anderson Head of Research ------------------------------ *From:* Nikesh B. Simmandree <nikeshbs(a)outlook.com> *Sent:* Monday, August 18, 2025 1:35 PM *To:* alac-announce(a)icann.org <alac-announce(a)icann.org>; alac(a)icann.org < alac(a)icann.org>; at-large(a)icann.org <at-large(a)icann.org>; afri-discuss(a)icann.org <afri-discuss(a)icann.org> *Subject:* Launch of The Internet Ecosystem Book Dear Community, I am thrilled to announce the launch of my book, *The Internet Ecosystem* — a comprehensive exploration of the history, architecture, governance, and future of the Internet. This book distills decades of technological evolution — from ARPANET and packet switching, to AI, Web3, quantum networks, and beyond — into a clear, engaging narrative accessible to both technical and non-technical readers *What the Book Covers* - *The Past:* How Cold War research, ARPANET, and packet switching gave birth to the Internet we know today. - *The Present:* The intricate roles of ISPs, backbone providers, cloud infrastructure, AI, cybersecurity, and global governance shaping our daily online experiences. - *The Future:* Insights into 5G/6G, blockchain, immersive technologies, quantum security, and the Internet in 2050. With *49 detailed chapters*, the book provides a definitive yet approachable reference for students, professionals, policymakers, and curious readers alike. My mission with *The Internet Ecosystem* is to make the Internet’s complexity understandable — showing not only *how* the Internet works, but also *why* it matters and has become one of the most transformative human inventions — while sparking dialogue on how we build a secure, inclusive, and sustainable digital future. In the 21st century, understanding the Internet is not optional — it’s essential. Whether you’re a business leader, policymaker, educator, student, or everyday Internet user, this book provides the context and clarity you need to navigate the opportunities and challenges of our connected world. *Get Your Copy* *The Internet Ecosystem* is now available: https://payhip.com/b/hfvYg Thank you, Best Regards, Nikesh B. Simmandree +230-5-907-3413 nikeshbs(a)outlook.com This message and its attachments are intended only for the person or entity to which it is addressed and are strictly confidential. If you have received this in error, please delete it from any devices after having informed the sender.

3 2

Co-chair selection for the RIPE DNS working group
by Moritz Müller 26 Jan '26

26 Jan '26

Dear DNS-WG, In accordance with the chair selection process we announce that the term of one of our co-chairs (Moritz Müller) will expire at the upcoming RIPE Meeting (RIPE 92, Edinburgh) 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). I (Moritz) reached my final number of terms and cannot volunteer any more for a new term. I had a great time as a co-chair and I would like to thank the community for their support in the last years. To volunteer yourself or nominate someone else, please send a mail to <dns-wg-chairs AT ripe.net> before end of Sunday 15 March 2026 (UTC). 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 Monday 16 March 2026. Discussion and support (or opposition) for each candidate can then be offered on the list. At the DNS working group session at RIPE 92, Ulrich and Yevheniya hope to announce consensus based on the mailing list discussion. Timeline Monday, 26 January 2026 This call for volunteers posted to the dns-wg mailing list Sunday, 15 March 2026 Deadline for volunteers/nominations Monday, 16 March 2026 List of candidates and call for support posted to the mailing list Monday, 18 May 2026 Deadline for showing support for candidates/volunteers on the mailing list Thursday, 21 May 2026 DNS WG session at RIPE 92 (still subject to change) 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. As always, please feel free to reach out to any of the co-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. -- Moritz Müller for the RIPE DNS working group co-chairs (Ulrich, Yevheniya and me)

1 0

AuthDNS anycast cluster IPv6 renumbering completed
by Anand Buddhdev 15 Jan '26

15 Jan '26

Dear colleagues, During RIPE 90 in May 2025, we announced that we would renumber our AuthDNS anycast cluster's IPv6 addresses, to ease various operational aspects of this service. The renumbering is now complete. The previous /48-sized prefix has been withdrawn completely, and most of the clean up work is done. We are in the process of returning this address space to the RIPE NCC's pool of unallocated address space. Regards, Anand Buddhdev RIPE NCC

1 0

Seeking advice: API-friendly authoritative DNS stack for a domain reseller platform
by v0 01 Jan '26

01 Jan '26

Hi DNS WG, I’m looking for advice from operators who run authoritative DNS at scale. I’ve been building a domain reselling platform for ~2 years. Today, we manage customer DNS zones via the individual registrar/provider APIs (multiple upstreams). Operationally it’s painful: high/variable latency, inconsistent semantics, and unpredictable failures. Long-term, we’d like to operate our own authoritative DNS service (geo-distributed, e.g. ns1/ns2/ns3) and have customer domains delegate directly to our nameservers. The challenge: I’m struggling to find a “right-sized” authoritative DNS stack that is API-first (or at least automation-friendly) without having to build an entire DNS control plane from scratch. What we’re looking for: - Clean, automatable zone + record lifecycle (create/retrieve/update/delete) via API or well-supported automation interfaces - Preferably open standards / minimal vendor lock-in - DNSSEC support What we’ve considered so far: - BIND / NSD / Knot: solid, but “no native API” makes dynamic management feel awkward at scale or require custom workarounds (which often rely on consistency from provider-side which tends to cause issues) - PowerDNS: seems powerful, but may be heavier than we need (happy to be convinced otherwise) - Managed (Cloudflare / NS1 etc.): technically great, but cost/lock-in doesn’t fit our reseller model, also, we are fans of self-hosting in the Hetzner Cloud Questions for the group: 1. If you were starting this today, what stack (authoritative server + control/management layer) would you recommend for this kind of product? 2. Are there established open-source “control planes” or patterns people use (e.g., RFC2136 dynamic updates, catalog zones, GitOps-style zone generation, database-backed auth, etc.) that work well in practice? 3. Any pitfalls you’d warn about when turning authoritative DNS into a customer-facing service? Happy to share more details (expected zone counts, update rates, deployment model) if that helps. Thanks a lot in advance, Sebastiaan

1 0

Re: Welcome to the "dns-wg" mailing list
by James Garner 22 Dec '25

22 Dec '25

How do I fix a DNS record with the following error? The CNAME record for www.fbclexmo.com has incorrect value "ghs.googlehosted.com". Change this record." ________________________________ From: dns-wg-request(a)ripe.net <dns-wg-request(a)ripe.net> Sent: Monday, December 22, 2025 12:55 PM To: jdgarner2022(a)gmail.com <jdgarner2022(a)gmail.com> Subject: Welcome to the "dns-wg" mailing list Welcome to the "dns-wg" mailing list! To post to this list, send your message to: dns-wg(a)ripe.net You can unsubscribe or make adjustments to your options via email by sending a message to: dns-wg-request(a)ripe.net with the word 'help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You will need your password to change your options, but for security purposes, this password is not included here. If you have forgotten your password you will need to reset it via the web UI.

2 1

Multi-Stakeholder Forum on Internet Standards Deployment
by MARTIN Ruediger 27 Nov '25

27 Nov '25

Hi all, The European Commission is setting up a Multi-Stakeholder Forum on Internet Standards Deployment, looking into strengthening the deployment of existing standards and operational best practices in four areas: - IPv6 - modern E-mail communication standards - DNS security - Routing security & hygiene The initiative was presented during its conceptual phase at RIPE 90 in the cooperation working group. The idea is to bring together valuable deployment expertise to capture proven approaches in multi-stakeholder guidelines that support broad and coordinated adoption across sectors. Participation is open to anyone with relevant experience and interest. More information and how to join: https://digital-strategy.ec.europa.eu/en/news/european-commission-seeks-par… Some of you may have seen this elsewhere; sharing it here as well since it may be relevant to this list. Best, Rüdiger ---- Rüdiger MARTIN Internet Governance [cid:image001.jpg@01DC5FB5.A87017F0] European Commission DG Communications Networks, Content and Technology (CONNECT) L-51 DCS B-1049 Brussels/Belgium +32 2 298 82 50 Ruediger.MARTIN(a)ec.europa.eu<mailto:Ruediger.MARTIN@ec.europa.eu>

1 0