DNS concepts
The DNS knowledge needed to define safe Domain0 connection intents.
Your product supplies the domain and required DNS records. Domain0 detects the customer's provider, shows the exact proposed changes, applies them when a verified automatic path is available, and checks every authoritative nameserver before reporting success.
DNS records
Supported record types, field rules, and examples.
Email authentication
Create SPF, DKIM, and DMARC intents safely.
Provider limitations
Design for automatic and guided provider paths.
Domain and host
intent.domain is the exact zone or subdomain the customer is connecting.
Each record host is relative to that domain:
| Intent | Host | Effective name |
|---|---|---|
example.com | @ | example.com |
example.com | www | www.example.com |
example.com | _dmarc | _dmarc.example.com |
app.example.com | @ | app.example.com |
Do not repeat the intent domain inside host.
Authoritative verification
Recursive resolvers can cache different answers. Domain0 considers a required record propagated only when every discovered authoritative nameserver returns the expected value. Until then, the connection remains pending and can be reopened safely.
Existing records
Domain0 reads provider state before applying automatic changes and displays an exact plan for confirmation. Destructive replacements require explicit confirmation. Guided setup shows the same effective records and verifies the result against authoritative DNS.