Domain troubleshooting
Start with the CLI, which looks up every record live:
spacepost domains doctor acme.comOr compare by hand with dig:
dig +short CNAME a1b2c3d4e5f6._domainkey.acme.comdig +short MX send.acme.comdig +short TXT send.acme.comdig +short TXT _dmarc.acme.comThe domain stays pending or not_started
Section titled “The domain stays pending or not_started”| Cause | Fix |
|---|---|
| Records not created yet, or DNS has not propagated | Wait 10 to 30 minutes, then call POST /domains/{id}/verify. TTLs of an hour or more can delay it. |
Domain name doubled (a1b2._domainkey.acme.com.acme.com) |
Your DNS provider appends the domain automatically; enter only the relative name (a1b2._domainkey). Check with dig. |
Name missing the domain (a1b2._domainkey is unresolvable) |
Your provider needs the full name (a1b2._domainkey.acme.com), common with Route 53. |
| Cloudflare proxy on | CNAME records for DKIM must be DNS only (grey cloud), not proxied. |
| Trailing dot or stray whitespace in the value | Re-paste the value exactly. |
| Quotes around TXT value | Enter the value without quotes. |
Conflicting existing record on send |
A CNAME on send.acme.com cannot coexist with MX/TXT. Use a different custom return path. |
| Two SPF records on the same name | Merge them into one TXT value. Only one v=spf1 record per name is allowed. |
The domain turned failed
Section titled “The domain turned failed”SpacePost gives up on a domain whose DNS has not appeared after 72 hours. Fix the records, then call verify again; the status returns to pending and then verified.
invalid_from_address
Section titled “invalid_from_address”403 invalid_from_address: “The example.com domain is not verified.” The domain in from must be a verified domain on your team, or a subdomain of one. Check for typos and for the wrong team’s API key.
Domain already registered
Section titled “Domain already registered”A domain can belong to only one team. If you re-registered a domain after leaving an old team, delete it there first or contact support.
Return path verified but DMARC fails
Section titled “Return path verified but DMARC fails”Open a received message’s headers (Gmail: Show original) and check Authentication-Results. You want dkim=pass header.d=acme.com and spf=pass with smtp.mailfrom=send.acme.com. If SPF shows amazonses.com, the return-path records are missing or not yet verified.
Still stuck
Section titled “Still stuck”Email support@spacepost.dev with the domain name and the output of spacepost domains doctor.