Insights:Business Email Domain Binding: MX, SPF, DKIM Setup
Prepare Before Binding
- Domain management permissions.
- Server address, port, and account provided by the email service provider.
- Screenshot or export of current DNS records.
- List of existing emails, aliases, and groups.
- A testable external email address.
Back up your existing MX, SPF, and DKIM records first. Overwriting old records directly may cause your old email to stop receiving messages immediately.
What Each Record Type Does
| Record | Purpose | Common Mistakes |
|---|---|---|
| MX | Tells where to deliver email | Wrong priority, old MX not removed |
| SPF | Authorizes which servers can send on your behalf | Multiple SPF records coexisting, syntax errors |
| DKIM | Adds a signature to emails | Mismatched selector or public key |
| DMARC | Defines how to handle authentication failures | Starting with p=reject immediately |
| Auto Discover | Allows clients to configure automatically | Omitting it causes Outlook configuration failures |
Use the values specified in your email service provider's console. Do not copy someone else's domain or outdated tutorials.
Recommended Configuration Order
- Create email accounts, aliases, and groups first.
- Add SPF, confirming only one valid record remains.
- Add DKIM, verifying the selector and public key match the provider.
- Add MX, checking priority and primary/backup relationships.
- Add DMARC, starting with a monitoring policy and confirming reports are normal.
- Configure Auto Discover and test the client.
- Verify sending, receiving, and authentication one by one.
Lower the TTL First, Then Switch Records
Lower the TTL for MX and authentication records in advance to leave room for propagation. After switching, don't delete old records right away—monitor for at least one business cycle.
Verification Commands
dig +short MX example.com
dig +short TXT example.com
dig +short TXT selector._domainkey.example.com
dig +short TXT _dmarc.example.com
Key things to check:
- Whether MX points to the current provider.
- Whether there is only one SPF record and whether it includes the current sending IP.
- Whether DKIM can resolve the public key.
- Whether DMARC has a
ruareport address.
Sending/Receiving Verification
- Internal mail exchange.
- External emails coming in.
- Send from new email addresses and check whether SPF/DKIM/DMARC passes.
- Whether mobile and desktop clients can log in.
- Whether old addresses, aliases, and groups can still receive mail.
- Any anomalies with spam folders or bounces.
Common Pitfalls
- Adding only MX without configuring SPF/DKIM — emails end up in spam.
- Two SPF records coexisting — authentication fails outright.
- Wrong DKIM selector — signature cannot be found.
- DMARC set to reject from the start — even legitimate mail gets bounced.
- Old MX not removed — mail delivery becomes intermittent.
- Auto-discovery misconfigured — clients repeatedly ask for passwords.
Boundary Cases
DNS propagation is affected by TTL and recursive caching, so we cannot guarantee global生效 immediately after saving. Control panel field names vary across email providers; follow your provider's documentation when filling them out. When managing multiple domains, subdomains, or cross-border sending/receiving, we recommend running a small-scale test first.
Related reading: