Reliable business email starts with more than creating mailboxes. This checklist explains how to connect a domain to email hosting, publish the essential MX, SPF, DKIM, and DMARC records, manage users and aliases, and troubleshoot common authentication and delivery problems without tying the process to one provider.
Overview
A business email hosting setup has several separate parts. The email provider stores and delivers messages; your domain registrar or DNS host publishes the records that tell other systems where to deliver mail and how to evaluate messages; and your mailbox-management process controls users, aliases, forwarding, storage, and access.
These parts must agree. MX records identify the servers that receive mail for your domain. SPF states which systems are allowed to send mail on behalf of the domain. DKIM adds a cryptographic signature to outgoing messages. DMARC tells receiving systems how to evaluate SPF and DKIM together and where to send aggregate or forensic reports, if reporting is configured.
Before changing DNS, collect the exact record values from your email host. Record names, targets, selectors, TTL guidance, and verification steps vary between providers. Do not copy a record from a different service merely because it looks similar. If your website and email use different providers, update only the email-related records and preserve website records such as A, AAAA, and CNAME entries.
For broader background, see DNS Records Explained: A Practical Guide to A, CNAME, MX, TXT, and More.
Checklist by scenario
1. Setting up a new domain email service
- Inventory the domain. Confirm the exact domain and any subdomains that will send mail. Verify who controls authoritative DNS and ensure an administrator can access both the DNS management panel and the email hosting console.
- Create the organization and mailboxes. Add the primary administrator, create user mailboxes, and define shared addresses such as support@, billing@, or sales@. Use individual accounts for people who need sign-in, rather than sharing one password.
- Publish MX records. Remove obsolete MX records only after confirming that the new service is ready. If old and new mail services are left active unintentionally, delivery can become inconsistent. Follow the provider's exact priority values and hostnames.
- Publish SPF. Add the provider's SPF TXT value at the root of the domain unless its instructions specify another name. A domain should normally have one effective SPF policy. If another service already sends mail, combine authorized mechanisms according to both providers' instructions instead of publishing a second SPF record.
- Enable DKIM. Generate or obtain the DKIM public key from the email host. Publish it under the supplied selector, often as a TXT or CNAME record, then activate signing in the provider console. The selector is part of the DNS name, so a typo can cause verification to fail even when the key itself is correct.
- Start DMARC carefully. Begin with a monitoring policy, commonly represented by
p=none, while you identify legitimate senders and review reports. Move toward a stricter policy only after confirming that important mail passes authentication and alignment. Use the provider's current guidance for reporting addresses and privacy considerations. - Test before migration. Send messages to several external test accounts, reply to them, and test inbound delivery. Check message headers for SPF, DKIM, and DMARC results rather than relying only on the sender's view of the message.
2. Adding a new sender, newsletter tool, or application
List every system that sends mail using the domain: the main mailbox provider, website forms, CRM, invoicing software, marketing platform, monitoring tools, and application servers. For each sender, document its sending domain or subdomain, SPF requirement, DKIM selector, return-path behavior, and DMARC alignment.
Prefer a dedicated subdomain for bulk or application mail when the provider supports it. This separates operational mail from person-to-person correspondence and makes troubleshooting more precise. Do not add an unverified sender to SPF simply because it appears in a setup guide; confirm that the business actually uses the service.
3. Onboarding or offboarding staff
- Create a unique mailbox and require a strong, unique password or the organization's supported sign-in controls.
- Set recovery methods and, where available, multi-factor authentication before handing over access.
- Use aliases for role-based addresses when no separate login or mailbox storage is required.
- Set forwarding only for a documented business reason, and review external forwarding rules because they can expose sensitive mail.
- When a user leaves, suspend or remove access, preserve required business data, transfer ownership of relevant files or calendars, and redirect role addresses deliberately.
4. Moving from one email provider to another
Lower the risk of interruption by preparing the new mailboxes and authentication records before changing MX. Export or migrate existing messages if retention matters, record current aliases and forwarding rules, and reduce DNS TTL in advance only if your DNS host supports that workflow and you understand the effect.
Keep the old service available during a planned overlap where practical. After changing MX, test delivery from multiple networks and external providers. Once mail is consistently arriving at the new service, remove obsolete MX, SPF inclusions, DKIM records, and forwarding rules. Review DMARC reports after the change because forgotten applications often appear there.
What to double-check
| Record or setting | Purpose | Checks before publishing |
|---|---|---|
| MX | Directs incoming mail to the receiving service | Use the exact targets and priorities supplied by the provider; remove obsolete entries only when migration is ready. |
| SPF TXT | Lists permitted sending systems | Keep one effective SPF policy, include every legitimate sender, and stay within the provider's lookup and syntax guidance. |
| DKIM | Signs outgoing messages and supports sender validation | Copy the selector and key or CNAME exactly; enable signing after DNS verification. |
| DMARC TXT | Defines handling and reporting for authentication failures | Start with a monitoring approach, confirm alignment, and use a reporting address that the organization can monitor. |
| TXT verification | Proves domain control to a service | Do not delete unrelated verification records used by websites, certificates, or other platforms. |
DNS interfaces use different labels for the same fields. The root domain may appear as @, a blank host, or the full domain name. A record value may require a trailing dot, quotation marks, or neither. Follow the interface's format and check how it displays the saved value.
Authentication results also depend on alignment. A message can pass SPF for one envelope sender while using a different visible From domain. DKIM can pass for a signing domain that does not align with the visible From domain. DMARC evaluation considers these relationships, so inspect complete headers and the provider's authentication report rather than checking only whether SPF or DKIM says “pass.”
Use a DNS lookup tool, the email provider's verification screen, and test messages with full headers. DNS changes can take time to appear at different resolvers, and a local cached result may not represent what an external recipient sees.
Common mistakes
- Publishing two SPF records. Multiple SPF TXT records at the same domain can make SPF evaluation fail. Combine authorized services into one policy when technically appropriate.
- Leaving old MX records in place. This can send some mail to a retired service. Keep only the intended receiving path once the migration is complete.
- Using a copied DKIM selector. DKIM selectors are provider- and domain-specific. A selector from another domain or account will not validate your messages.
- Jumping straight to a restrictive DMARC policy. Legitimate website forms, billing platforms, and newsletters may not yet be aligned. Monitor first, correct senders, then tighten the policy in stages.
- Forwarding mail without testing authentication. Forwarding can alter the path or message handling and may affect SPF results. Test forwarded messages and consider provider-supported forwarding controls.
- Confusing aliases with mailboxes. An alias may deliver to an existing mailbox but may not provide separate storage, login credentials, or independent sending identity.
- Ignoring quotas and retention. Define what happens when a mailbox reaches its limit, how long messages are retained, and who can approve archival or deletion.
- Changing DNS during an incident without a record of the original state. Export or document existing records first. This makes rollback and investigation safer.
If the problem affects the website as well as email, separate the investigation. Consult the Website Uptime Monitoring and Incident Response Checklist for a broader incident workflow. For domain ownership, renewal, and transfer risks, use the Domain Registration and Renewal Guide.
When to revisit
Review this checklist whenever you add a sender, onboard or offboard staff, change email hosting providers, move DNS management, launch a new website form, or receive authentication-failure reports. It is also useful before seasonal planning cycles, major campaigns, domain transfers, and changes to mailbox quotas or retention rules.
At least twice a year, review the domain's MX, SPF, DKIM, and DMARC records against an inventory of services that still send mail. Remove abandoned vendors, confirm that reporting addresses are monitored, and check whether the email provider has changed its record format or verification process. Treat a change to a provider's workflow as a reason to verify the entire setup rather than editing one record in isolation.
Keep a simple change log containing the date, person responsible, provider, records changed, test recipients, and observed authentication results. A practical final check is: send an outbound message, confirm it arrives, inspect SPF/DKIM/DMARC headers, reply to it, test a role alias, test a forwarding rule if one exists, and verify that an intentional unknown sender is not being treated as an approved service. This small routine turns domain email setup from a one-time task into maintainable DNS management.