Domain Connect (protocol)

Domain Connect is an open protocol, stewarded by the Domain Connect Association, that lets a service apply DNS templates at a user's DNS provider through a consent screen the provider hosts. It removes manual record entry where supported, but only a subset of registrars and DNS hosts implement it.

Attribution: Domain Connect is an open protocol of the Domain Connect Association. Custom Domain is not affiliated with, or endorsed by, the Domain Connect Association. This glossary entry describes the protocol for reference.

What the protocol does

Domain Connect exists to remove one specific piece of friction: a user setting up a service, such as email or a website builder, should not have to copy DNS records by hand into their registrar's console. The protocol defines how a service provider can describe the records it needs and how a DNS provider can apply them after showing the user a consent screen on the DNS provider's own site.

The moving parts:

• Templates. A service provider publishes a template describing the DNS records its service needs, with variables filled in per customer. Each participating DNS provider has to support a template before it works there.
• Discovery. Given a domain, the service queries DNS to learn whether the domain's DNS provider supports the protocol and where its settings endpoint lives.
• Synchronous flow. The user is redirected to the DNS provider's hosted page, signs in, approves the change, and the provider applies the template.
• Asynchronous flow. An OAuth style grant lets the service apply and update records over time without sending the user back through the consent screen.

The specification is an open standard published under the MIT license, designed and maintained by a community of developers across multiple companies. Details and participant lists are at domainconnect.org.

Adoption and its limits

The protocol works well where it is implemented, and that qualifier carries a lot of weight.

• Only some DNS providers support it. Adoption is concentrated among a subset of registrars and DNS hosts. GoDaddy, where the protocol originated, and IONOS are among the notable implementers. Many widely used providers have never adopted it, so a service cannot rely on it as its only setup path.
• Templates require coordination. A service provider's template must be published and then supported by each DNS provider individually, which takes time and is not guaranteed.
• Fallbacks are unavoidable. When a user's domain sits at a provider without support, the experience degrades to manual instructions unless the service has built other paths.

Domain Connect compared to broader approaches

The protocol is one way to automate DNS setup for end users. It is not the only one, and in practice it covers the smallest share of providers.

Approach	How it works	Coverage
Domain Connect protocol	Consent screen hosted by the DNS provider applies a published template	Only DNS providers that implement the protocol
One-click provider authorization	The service integrates each provider's own login and API directly	Set by the service's integration list, independent of any protocol's adoption
API token	The user pastes a scoped token from their provider	Any provider with a management API
Guided manual flow	Step by step instructions with automatic verification	Every provider

Custom Domain takes the broader route: 63 DNS and registrar providers are covered through one-click provider authorization, API tokens, or a guided manual flow that verifies records automatically, and the connection flow picks the best available path for each domain. The result is the same one-click feel where deep integrations exist, with a working path everywhere else. See how it works for the connection flow, the wider category definition in custom domains as a service, and the full capability list on features.