DNS concepts
Provider limitations
Build one integration that remains usable across different DNS providers.
DNS providers differ in authorization, record support, API behavior, and nameserver capabilities. Domain0 Connect selects the safest currently available path for the detected provider.
| Provider path | Customer experience |
|---|---|
| Verified automatic | Authorize, review the exact plan, confirm, and wait for verification |
| Domain Connect | Approve the provider-hosted consent flow, then return for verification |
| Guided setup | Copy the exact records into the provider dashboard, then verify |
| Unverified | Use guided setup without collecting provider credentials |
See the current provider catalog for customer-visible coverage. Catalog presence means that Domain0 recognizes and guides that provider; it does not automatically mean API-based setup is enabled.
Common differences
- Some providers do not expose an API for DNS changes.
- OAuth, API-token, and account-credential flows require different consent.
- Apex CNAME behavior varies and may rely on provider-specific flattening.
- Providers may normalize TTLs, trailing dots, and TXT presentation.
- Nameserver modification can be unsupported or intentionally unavailable.
- Automatic setup may be temporarily unavailable while guided setup remains usable.
Do not branch your integration by provider
Create the same connection intent for every customer. The embedded flow owns provider detection, authorization choice, and guided fallback.