Blog
Latest posts from Pax
← BackHow to point your domain’s DNS to Pax Mail
New
How to point your domain’s DNS to Pax Mail
Follow the steps below — they take just a few minutes at most registrars.
If you already know your way around DNS, simply replace your existing mail-related records with the ones shown on the Pax “DNS” tab for your domain and you’re done.
Otherwise, use the detailed guide.
1. Find your Pax DNS checklist
- Sign in at paxmail.cc.
- Go to Domains ( https://paxmail.cc/domains ).
- Click the domain you’re switching.
- On the domain page, open the DNS tab. You’ll see a table headed “A list of all DNS fields your domain needs to send/receive mail with Pax.”
Everything you need to copy is in the Expected Value column.
2. Open your domain-host’s DNS editor
This is usually your registrar (e.g., GoDaddy, Namecheap) or the provider hosting your authoritative nameservers (e.g., Cloudflare, AWS Route 53).
- Sign in to your registrar/host.
- Locate the DNS or Zone File editor for the same domain.
3. Replace old mail records
Delete or disable every existing MX, SPF, DKIM, DMARC, Autodiscover, Autoconfig, and SRV record for the domain (if present).
⚠️ Leaving old mail records active can cause delivery failures or security warnings.
4. Add Pax records exactly as shown
Add each record below one-for-one in your DNS editor; delete any conflicting old record first.
- MX records (all required)
- @ → mx1.paxmail.cc priority 10
- @ → mx2.paxmail.cc priority 20
- @ → mx3.paxmail.cc priority 30
- @ → mx1.paxmail.cc priority 10
- CNAME: Autodiscover
- autodiscover → mail.paxmail.cc
(Optional, but Outlook uses it.)
- autodiscover → mail.paxmail.cc
- CNAME: Autoconfig
- autoconfig → mail.paxmail.cc
(Optional, but Thunderbird uses it.)
- autoconfig → mail.paxmail.cc
- TXT: SPF
- @ → v=spf1 a mx ~all
- @ → v=spf1 a mx ~all
- TXT: DMARC
- _dmarc → v=DMARC1;p=quarantine;pct=100
- _dmarc → v=DMARC1;p=quarantine;pct=100
- TXT: DKIM
- dkim._domainkey → v=DKIM1;k=rsa;t=s;s=email;p=<long RSA key from Pax table>
- dkim._domainkey → v=DKIM1;k=rsa;t=s;s=email;p=<long RSA key from Pax table>
- SRV (optional)
- _autodiscover._tcp → 0 1 443 mail.paxmail.cc
(Skip if your registrar doesn’t support SRV.)
- _autodiscover._tcp → 0 1 443 mail.paxmail.cc
An aside - Understanding the SRV record format A single SRV record line shown by Pax looks like: _autodiscover._tcp.example.com. 0 1 443 mail.paxmail.cc. Breakdown (in order):
_autodiscover — service label: identifies the feature (autodiscover) the client is looking for. _tcp — protocol: TCP or UDP. example.com. — domain that owns the record (trailing dot = absolute FQDN). (replace example.com with your domain) 0 — priority: lower numbers are tried first. 1 — weight: load-balances hosts that share the same priority (0 – 65535). 443 — port the service listens on. mail.paxmail.cc. — target host the client should connect to (must resolve via A/AAAA or CNAME).
Registrar tips
- Some UIs split these fields into separate boxes; others expect a single space-separated string.
- If your provider requires TTL, place it immediately after the domain segment.
- The trailing dots (.) after domain and target are not required everywhere; add them only if your registrar’s docs say so.
Tips
- Use @ (or leave the Name/Host field blank) to represent the root of the zone if your DNS editor does so.
- Keep priorities for MX exactly as listed.
- A TTL of 300–3600 seconds is ideal if editable.
5. Save & wait for propagation
DNS changes commonly take 15 – 30 minutes but can require up to 24 hours worldwide. During propagation, both your old and new servers may receive mail. That’s normal.
6. Test email flow
- Send yourself a message from an external account (e.g., Gmail) → confirm it lands in your Pax inbox.
- Reply from your Pax address → confirm SPF, DKIM, and DMARC all pass (Gmail shows this under “Show original”).
FAQ
- I can’t add SRV/CNAME records. Skip optional records; mail will still work.
- My registrar needs trailing dots. If required, enter mx1.paxmail.cc. (dot at the end).
- Still seeing “Pending” in Pax after 24 h? Check for typos, duplicated records, or hidden legacy MX records.
That’s it! Once everything resolves, all mail for your domain will route through PaxMail’s reliable, secure platform.
Follow us on social media: