Connect a domain
A mail platform takes a customer’s domain in four steps: the customer proves the domain is theirs, the platform sets it up on its mail server, the customer publishes the records the platform asks for, and the platform checks them at two public resolvers until both see every one. The three domains below are made up and their DNS is simulated, so a change reaches Cloudflare at once and Google one check later, as a real change propagates.
Moving from another provider. The domain gets its mail at another provider today. Its MX, SPF and autodiscover all point there, and it has not proved that it is ours.
- Health
- …
- State
- …
- Records right
- …
- Checks run
- 0
- at Cloudflare and Google
The records
Every record the platform asks for, looked up at Cloudflare and at Google. A record is right only when both resolvers see it.
| Status | Name | Type | What the check found | Seen at |
|---|
The fixes
What would make every record right, as a zone file to paste at the DNS provider.
Remove these records
| Name | Type | Value |
|---|
Ownership
The platform makes a token from the account and the domain with a key only it holds. The record proves the customer controls the domain’s DNS, and a token made for another account proves nothing.
Lifecycle
- Waiting for proof
- Provisioning
- Waiting for records
- Active