Domain Connect — Product Edition: Service Providers¶
Version: 1.0 | Last updated: October 2026
Author: Pawel Kowalik, Co-Author of Domain Connect specification
Sources: IETF draft-ietf-dconn-domainconnect-04 (Oct 2026), stats.domainconnect.org, Domain Connect Support Stats (Beta), Templates repository README, ROW 2025 presentation (Sep 2025), CENTR Jamboree 2025 presentation (May 2025)
About This Edition¶
This edition is for product managers at service providers — SaaS platforms, email and productivity suites, website builders, e-commerce platforms, marketing tools — anyone whose product asks customers to bring their own domain. It helps you decide whether to integrate Domain Connect and convince your team, your engineering leads and your CEO.
It answers four questions in order:
- Why should we do this? — the problem, the value, and how to size it for your funnel
- What exactly would we build? — the components, phases, team and ongoing operations
- What could go wrong? — coverage, dependencies, security and the objections you will hear
- How do I get a yes? — a 60-second pitch, a one-page executive brief and how to tailor the message per audience
You do not need to read the protocol specification to use this edition. Where technical depth helps a decision, the pages link to the relevant section.
Implementing it yourself or handing over to engineering? See the Implementers Edition. Working on the DNS provider side? See the Product Edition: DNS Providers.
The One-Paragraph Summary¶
Every time your onboarding says "now add these DNS records at your registrar", you lose customers — about half of users fail manual DNS setup, and the ones who make it often end up in your support queue with records entered wrong. Domain Connect lets you skip that step. You describe the records your service needs in a template, publish it once, and when a customer's DNS provider supports it, your onboarding shows a "Connect automatically" button: the customer logs in at their DNS provider, approves, and is sent back to you with DNS configured correctly. 294 DNS providers, including GoDaddy, IONOS and Cloudflare and covering ~42% of scanned domains, already support it, and 1,436 service providers have already published templates. The protocol has been in production since 2016 and is on the IETF Standards Track.
Reading Paths¶
| You have… | Read |
|---|---|
| 15 minutes before a meeting | Executive Brief |
| One hour to form your own opinion | Business Case → Scope of Work → Risks & Objections |
| An afternoon to prepare a proposal | All four product pages, then How It Works, Template Use Cases and Adoption & Ecosystem |
| A hand-over to engineering | Getting Started: Service Provider and the Implementers Edition |
Key Numbers for Your Slides¶
| Metric | Value |
|---|---|
| Users who fail manual DNS setup (Microsoft 365) | ~50% |
| DNS records needed for Microsoft 365 | 7–15 |
| Help sites Microsoft maintains for this step | 16 (10 registrar-specific) |
| Support training needed for manual setup | 40 minutes |
| DNS providers live | 294 (incl. GoDaddy, IONOS, Cloudflare, Squarespace Domains, WordPress.com, Plesk) |
| Share of scanned domains on supporting DNS providers | ~42% (September 2026) |
| Service providers with templates | 1,436 (2,207 templates) |
| Notable service providers | Microsoft 365, Google Workspace, Apple iCloud+, Shopify, Squarespace |
| In production since | 2016 |
| IETF DCONN working group approved | October 2025 |
Ecosystem statistics from Domain Connect Support Stats (Beta) and stats.domainconnect.org (2026-10-29).
Document Map¶
| Document | What it gives you |
|---|---|
| Business Case | Value levers, how to size the opportunity with your own funnel data, KPIs |
| Scope of Work | Components, build-vs-reuse, phasing, team, ongoing operations |
| Risks & Objections | Answers for your CTO, CISO, design, support and finance |
| Executive Brief | 60-second pitch, one-page brief, tailoring by audience, first steps after approval |
| 01 Problem & Context | DNS failure rates, the three-actor gap |
| 02 What Is Domain Connect | Definition, scope, what it is not |
| 03 How It Works | Flows, templates, discovery, consent |
| 05 Use Cases | What services use it for, including multi-step flows |
| 06 Value by Audience | Value for service providers, DNS providers, users |
| 07 Adoption & Ecosystem | Who is live, standardization timeline |
| 08 Security Model | Trust model, signing — for your security review |
| 13 Getting Started: Service Provider | The step-by-step integration guide your engineers will follow |
| 15 Template Use Cases | Which template pattern fits your product |
| Stories | First-person stories from a service provider CEO, PM and support manager |