Seamless Connect

Use cases

Neutral coordination across independently operated providers.

Use Cases

Seamless Connect is an open-source, nonprofit infrastructure project providing a neutral coordination layer between service providers, DNS providers, and registrars, initially focused on DNS configuration through Domain Connect.

Early industry participation includes Name.com (Identity Digital), Cloudflare, DigiCert, Datum.net, and Cloud 66.

These use cases describe the project's intended workflows. The initial focus is DNS configuration through Domain Connect; broader workflows are proposed or under development. Availability depends on the operation and participating provider integrations. Examples below illustrate protocols, proposals, and provider interfaces a workflow may employ; they do not imply implemented support. IETF drafts are works in progress, not finalized standards.

DNS Configuration (Domain Connect)

Configure DNS records across participating providers using Domain Connect templates and domain-owner authorization. For example, connect a domain to a hosting or email service without manually entering each record.

Initial focus: operationalizing Domain Connect through shared cross-provider coordination. Supported templates and operations depend on each provider integration.

Examples of applicable protocols and standards: Domain Connect, DNS UPDATE (RFC 2136), OAuth 2.0 (RFC 6749).

DNSSEC

Coordinate DNSSEC enablement between a registrar and an authoritative DNS provider, including publishing the delegation information needed to establish the chain of trust.

Discovery and pilot design: explore authorized coordination across independently operated providers using existing standards.

Examples of applicable protocols and standards: DNSSEC (RFC 4033, RFC 4034, RFC 4035), CDS/CDNSKEY (RFC 7344), RFC 8078, RFC 9615.

Primary / Secondary DNS

Configure primary and secondary DNS zones across providers so multiple authoritative providers can serve the same zone, improving resilience and availability.

Proposed workflow: coordinate zone provisioning, full and incremental zone transfers (AXFR/IXFR), TSIG configuration for transfer authentication, and synchronization setup across participating DNS providers.

Examples of applicable protocols and standards: AXFR (RFC 5936), IXFR (RFC 1995), DNS NOTIFY (RFC 1996), TSIG (RFC 8945), XFR-over-TLS (RFC 9103).

Domain Registration

Coordinate domain registration across participating providers while keeping the domain owner in control of authorization and provider selection.

Proposed workflow: coordinate registration requests through participating registrars, subject to their availability, policies, and supported operations.

Examples of applicable protocols and standards: EPP (RFC 5730 / RFC 5731), RDAP (RFC 9082 / RFC 9083) — read-only registration data, not registration transactions, registrar APIs (provider-specific).

Agent Bootstrapping

Publish agent discovery information through participating providers. This proposed use case aligns with the Foundation for Agentic Networks (FAN) mission by supporting open, interoperable discovery publication without favoring particular protocols or providers.

DNS-based

Publish agent discovery records through participating DNS providers, using the record formats required by the selected discovery protocol.

Examples of applicable protocols and standards: DNS-AID (IETF draft), Agent Identity and Discovery (AID) (IETF draft), Agent Name Service (ANS) (evolving DNS/PKI proposal with a GoDaddy implementation), DNSSEC (RFC 4033).

Non-DNS

Publish agent information through participating agent registries and other discovery systems, using their supported publication interfaces.

Examples of applicable protocols and standards: A2A Agent Cards, NANDA Index (agent discovery infrastructure) and AgentFacts (agent metadata), and other agent registries. Publication interfaces vary; these examples do not imply implemented Seamless Connect support.

Adjacent discovery system: the MCP Registry catalogs MCP servers; it is not an equivalent agent registry.

Proposed scope: authorized publication of discovery information. General agent communication, identity, and orchestration are outside this use case.

Build with the projectExplore documentation and integration guides ↗︎