DomainKit and Domain Connect

What the Domain Connect protocol does, why DomainKit does not implement it today, and what DomainKit does instead.

Domain Connect is a protocol. A service provider publishes a DNS template, a supporting DNS provider renders consent for it, and the customer applies it in the DNS provider’s own interface.

DomainKit is a library your application runs. It connects a provider through that provider’s API, builds a plan from the records your product needs, records approval for that exact plan, applies it, keeps a receipt, and observes DNS afterwards.

What DomainKit does not do

DomainKit does not implement Domain Connect. There is no Domain Connect provider adapter, no template publishing, and no plan to describe DomainKit as a replacement for the protocol. That work is parked, not in progress.

If your product’s setup is a fixed template on a DNS provider that already supports Domain Connect and hosts your template, the protocol does that job without a library.

What DomainKit does instead

DomainKit is built for the setup that continues after the first click:

• The record values differ per customer, per tenant, or per environment.
• The product needs to see whether the records are actually live, from the provider and from public DNS, and to say when to look again.
• The same provider access has to serve the customer’s next domain.
• Removing records later has to be as reviewed as adding them was.

Those are the pieces on plans, connections, verification, and cleanup.

For a side-by-side of the two mechanisms, see Domain Connect and DomainKit.