Domains
.mdSet up your domain’s DNS
Updated 1 Oct 2026
You bring a domain; SuperMailOS does the DNS. The exact records come from the mail server’s own zone — not a guessed template — so what you publish is what the server actually expects. You’ll either publish them with one click or copy-paste them, and we verify them live before anything can send.
Four steps, start to finish
Add your domain
In SuperMailOS, add your domain. We read the mail server's own zone and generate the exact MX, SPF, DKIM and DMARC records for it.
Publish the records
One-click publish on a supported provider (Cloudflare, DigitalOcean, Linode, Vultr, Hetzner DNS or Spaceship), or copy-paste the records into any other DNS host.
Verify live
Watch the records verify in the app. An unverified domain can't send, which prevents misconfigured mail from ever going out.
Start sending
Once verified, DKIM signing, DMARC reporting and new-domain warm-up run automatically from the first message.
The records you’ll add
| Record | What it does |
|---|---|
| MX | Routes inbound mail for your domain to our mail servers. |
| SPF (TXT) | Authorizes our sending infrastructure to send as your domain. |
| DKIM (TXT) ×2 | Publishes the public halves of your domain's two signing keys (one Ed25519, one RSA), so receivers can check our signature. |
| DMARC (TXT) | Sets the policy and points aggregate reports at us, so they're parsed into your dashboard. |
That’s the whole checklist: five records. The values are shown in the app, filled in for your domain. You never have to know a DKIM selector or hand-write an SPF string.
| Type | Host | Value | |
|---|---|---|---|
| MX | @ | mail.supermailos.com (priority 10) | |
| TXT | @ | v=spf1 mx ra=postmaster -all | |
| TXT | v1-ed25519-20260704._domainkey | v=DKIM1; k=ed25519; h=sha256; p=… | |
| TXT | v1-rsa-20260704._domainkey | v=DKIM1; k=rsa; h=sha256; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA… | |
| TXT | _dmarc | v=DMARC1; p=reject; rua=mailto:dmarc@supermailos.com; ruf=mailto:dmarc@supermailos.com |
One-click, or copy-paste
On Cloudflare, DigitalOcean, Linode, Vultr, Hetzner DNS and Spaceship, SuperMailOS can publish every record for you with one click — you paste an API token, we create the records, and the token is used once and never stored. On registrars with closed APIs (GoDaddy, Namecheap, Squarespace), you copy each record into their DNS panel; the app shows exactly what goes where.
Then we verify — before you can send
As you publish, the app checks each record live. A domain that hasn’t verified simply can’t send, which is the point: it stops half-configured mail from going out and damaging your reputation. Once green, DKIM signing, DMARC reporting and new-domain warm-up begin automatically.
Common snags
- An old MX still present. Remove records pointing at a previous provider, or inbound mail splits between two systems.
- Two SPF records. A domain may have only one SPF (TXT starting
v=spf1); a second one makes both invalid. Merge into the single record the app shows. - Propagation lag. DNS changes can take time to appear depending on your TTLs. Re-run verification; it clears once the record is visible.
Want the theory behind each record first? The complete guide to email DNS records walks through the whole chain. Then connect a mail app.
Was this page helpful?