Question 1

What does Domain0 actually do?

Accepted Answer

Domain0 is an embeddable SDK for connecting customer domains to your product. Your app supplies the domain and intended DNS records. Domain0 handles provider detection, the available authorization flow and DNS verification, then notifies your app when the connection is ready.

Question 2

Does Domain0 register or sell domains?

Accepted Answer

No. Domain registration, website hosting, and your product's billing stay separate. Domain0 is the connection layer between a domain a user already controls and the product they want it to point at.

Question 3

How does it know which provider a domain uses?

Accepted Answer

It resolves the domain's nameservers and matches them against a catalogue of provider adapters. Your code never branches on a vendor name: the SDK returns one typed connection model, and each provider's differences stay behind a tested adapter.

Question 4

What happens to records that would break mail?

Accepted Answer

They surface as conflicts before anything is written. If replacing an MX record would drop mail delivery, the change plan says so and the destructive path becomes an explicit choice rather than a silent overwrite.

Question 5

Does Domain0 need my customers' DNS passwords?

Accepted Answer

The method depends on the provider. Domain Connect uses provider-owned consent for the requested DNS changes. Other integrations may require a scoped token or provider credentials. When an automatic path is unavailable, guided manual setup remains an option.

Question 6

Can I self-host it?

Accepted Answer

Yes. The Apache-2.0 Go backend is designed to run with your own PostgreSQL and encryption keys, using the same SDK and API. Contact us for backend access while the public source release is being prepared. Provider setup and Domain Connect template approvals are still required for your deployment.

Question 7

What if the customer's provider has no adapter?

Accepted Answer

The flow falls back to guided manual setup rather than failing. Domain0 shows the exact records to create, formatted for that provider's control panel, and then verifies them the same way it verifies an automated change: by querying every authoritative nameserver until the record actually resolves. The customer ends up in the same verified state, just with a few more steps.

Question 8

How long does a domain take to go live?

Accepted Answer

That depends on the record's TTL and on how quickly the provider publishes the change, so it ranges from seconds to a few hours and is not something any connection layer can promise. What Domain0 does control is honesty about it: the connection stays in a propagation-pending state, and only moves to verified once the record is observed on every authoritative nameserver rather than after an optimistic delay.

Question 9

Which DNS providers are supported?

Accepted Answer

Availability depends on the provider, authorization method and requested records. Domain Connect also requires acceptance of the exact service template. A provider logo is not a guarantee of automatic setup; the SDK checks the available path and offers guided manual setup when needed.

Domain connections, built into your product.

From hostname to verified.

Find their DNS provider

Checking acme.com

Apache-2.0

Deploy your way

Provider-aware

Common questions.

Add domain connections to your product.