Skip to content
postnuvaDocumentation

A home on your domain.

DNS records tell the world where to deliver your mail and prove the messages you send are really yours. Publish these records at your DNS provider, then run verification in the dashboard.

Domain & DNS guideOwnership and delivery

Before you begin

  • A domain you own, with access to its DNS provider (where you manage records).
  • The domain added in postnuva — the dashboard generates the exact values to publish.
  • Your deployment’s mail hostname (for example mails.example.com) and generated DKIM key.
Values below are examples.

Replace example.com, the DKIM selector, and all record values with the ones your own installation generates. The record types and purposes are what stay the same.

The records

A complete setup uses five record types. Add the optional CNAMEs if you want friendly hostnames for mail clients.

TypeHost / NameExample valuePurpose
TXT@nubmail-verification=…Prove you own the domain.
MX@mail.example.com (priority 10)Route incoming mail to your server.
TXT (SPF)@v=spf1 mx ~allAuthorize your server to send.
TXT (DKIM)nub._domainkeyv=DKIM1; k=rsa; p=…Publish your signing key.
TXT (DMARC)_dmarcv=DMARC1; p=quarantine; rua=mailto:…Set your domain’s mail policy.
CNAME (optional)imap, smtp, popmails.example.comFriendly hostnames for mail clients.
  • Ownership (TXT) is checked first — the domain won’t verify until this resolves.
  • SPF, DKIM, and DMARC work together so receiving servers trust your mail and it stays out of spam.
  • Some providers want the host as @ for the root; others leave it blank. Both mean the same thing.

Publish and verify

  1. Copy the records

    Open your domain in the postnuva dashboard and copy each generated record.

  2. Add them at your DNS provider

    Create each record with the exact type, host, and value. Leave TTL at the default or 1 hour.

  3. Wait for propagation

    Changes are usually live within minutes but can take up to 24–48 hours worldwide.

  4. Run verification

    Back in the dashboard, run verification. Once ownership and mail records resolve, the domain is marked verified.

Check propagation yourself.

Use dig (or nslookup) to confirm a record is live before running verification.

check-dns.sh
Shell
# Check your records have propagated
dig +short MX example.com
dig +short TXT example.com
dig +short TXT nub._domainkey.example.com
dig +short TXT _dmarc.example.com

Troubleshooting

  • Domain won’t verify. Re-check the host and value match exactly — no extra quotes, spaces, or a trailing dot where the provider adds one. Then wait for propagation.
  • Mail lands in spam. Confirm SPF, DKIM, and DMARC all resolve and that you send from a mailbox on the verified domain.
  • DKIM not found. The selector host is nub._domainkey (use the selector your install shows). Some providers auto-append the domain, so don’t add it twice.
  • Clients can’t connect. Verify your CNAMEs point at the mail host and use the ports in the mail client guide.
Previous guideGetting startedYour next stepCreate an account