Setting up email on a custom domain involves more than adding an MX record. This reusable checklist explains how to configure MX, SPF, DKIM, and DMARC, verify each change, and troubleshoot bounces or spam placement across common email and sending providers.
Overview
A custom business email address, such as [email protected], depends on two connected systems: the mailbox provider that receives messages and the DNS records that tell the internet where to deliver and how to authenticate outgoing mail.
Use this order when completing a business email domain setup:
- Confirm domain ownership with your email provider.
- Configure MX records so incoming mail reaches the correct provider.
- Publish one SPF record listing approved senders.
- Enable DKIM and publish the provider-generated public key.
- Deploy DMARC, beginning with monitoring if the domain has existing senders.
- Test delivery and authentication from several mailboxes.
DNS changes may not appear everywhere immediately. Keep a record of the previous values, the new values, the date changed, and the provider responsible for each sending service. This makes troubleshooting and future DNS management substantially easier.
Before you start
- List every service that sends mail for the domain, including staff mailboxes, website forms, newsletters, invoices, support tools, and transactional applications.
- Identify the authoritative DNS host. It may be your registrar, cloud hosting provider, or a separate DNS platform.
- Ensure you can access the provider's administrator console and the domain's DNS management panel.
- Check whether an existing SPF, DKIM, or DMARC record is already present. Do not add a second record without understanding the first.
Checklist by scenario
Scenario 1: A mailbox provider such as Google Workspace or Microsoft 365
- Complete the provider's domain-verification step. This normally requires adding a temporary TXT record supplied in the administrator console.
- Replace or update the domain's MX records with the exact values shown by the provider. Google Workspace and Microsoft 365 can change their recommended values or provide tenant-specific details, so use the current administrator instructions rather than copying an old list.
- Add the provider's SPF include to the existing SPF policy. Typical provider patterns include
v=spf1 include:_spf.google.com ~allfor Google-managed sending orv=spf1 include:spf.protection.outlook.com ~allfor Microsoft-managed sending. Treat these as examples: confirm the value in the provider dashboard. - Generate or activate DKIM in the administrator console. The provider will give you a selector and a TXT or CNAME target. Publish the record exactly as supplied, including the selector and any required punctuation.
- After DKIM passes, publish a DMARC record such as
v=DMARC1; p=none; rua=mailto:[email protected]; pct=100. Use a monitored mailbox or reporting service forrua; do not use an address you cannot review.
Scenario 2: A website, application, or contact form sends mail
Do not assume that hosting the website also authorizes its server to send mail. Decide whether the form should send through the mailbox provider or a dedicated transactional provider. A dedicated provider usually supplies its own SPF include, DKIM CNAME records, and sometimes a return-path or tracking-domain record.
For Mailgun, SendGrid, or a similar service, begin in the sending-domain setup screen and copy the generated records. A safe template looks like this:
Type: TXT Host: @ or provider-specified host Value: v=spf1 include:PROVIDER-SPF ~all
Type: CNAME Host: PROVIDER-SELECTOR Value: PROVIDER-DKIM-TARGET
Type: CNAME Host: PROVIDER-RETURN-PATH Value: PROVIDER-RETURN-PATH-TARGETReplace every placeholder with the values generated for your account. Do not combine two complete SPF strings into two TXT records. Instead, merge authorized mechanisms into one policy, for example v=spf1 include:_spf.google.com include:sendgrid.net ~all, after confirming the services and their current instructions. Keep the number of DNS lookups within SPF's operational limit; if the policy becomes complex, use the provider's supported flattening or managed configuration rather than inventing a workaround.
Scenario 3: You are moving email to a new provider
- Lower the MX record TTL before the planned change if your DNS provider allows it, while keeping the old mailbox service active.
- Export or migrate existing mail before changing delivery.
- Configure the new provider's verification, MX, SPF, and DKIM records.
- Change MX records during a low-risk period and test both incoming and outgoing mail.
- Keep the old service available until delivery is confirmed and any migration hold period is complete.
For a broader domain move, separate the email change from a domain transfer or website migration where possible. This reduces the number of variables if mail stops arriving. The DNS records guide provides additional context on how website and email records coexist.
What to double-check
MX records
- There is no outdated MX record pointing to the previous provider.
- Priority values are entered as numbers and match the provider's instructions.
- The record is entered at the correct host, usually the root domain represented by
@. - You are editing authoritative DNS, not a disconnected DNS zone at your registrar.
SPF
- There is exactly one SPF policy for the domain.
- Every legitimate sending service is represented.
- The policy ends with an intentional qualifier such as
~allduring rollout or-allafter you have confirmed all senders. - Website hosting, CRM, marketing, and support platforms have not been overlooked.
DKIM and DMARC
- The DKIM selector in DNS matches the selector configured by the provider.
- The DKIM public key has not been wrapped, truncated, or altered by the DNS editor.
- DMARC alignment is considered: the visible From domain should align with the authenticated SPF or DKIM domain.
- DMARC reports go to an address that is monitored and appropriate for receiving automated reports.
Verification methods
Use your provider's built-in verification tool, a DNS lookup utility, and a controlled test message. Command-line checks can help:
dig MX example.com
dig TXT example.com
dig TXT _dmarc.example.com
dig TXT selector1._domainkey.example.comReplace example.com and selector1 with your domain and actual DKIM selector. Online DNS checkers and mail-testing tools can reveal missing records, syntax errors, SPF problems, and DKIM or DMARC results. Test from an address outside your own domain, then inspect the message's authentication results in the recipient mailbox.
Common mistakes
- Adding a second SPF record: merge the policy instead of publishing multiple
v=spf1records. - Using old provider examples: provider hostnames and setup workflows change. Copy current values from the account that will send mail.
- Changing MX before preparing the new mailbox: messages may be rejected, delayed, or delivered to an unconfigured service.
- Publishing DMARC too aggressively: a strict enforcement policy can affect legitimate mail when an overlooked sender is not authenticated. Start with monitoring, review reports, and increase enforcement deliberately.
- Assuming SPF proves the visible sender: SPF authenticates an envelope sender, while DKIM signs message content and DMARC evaluates alignment with the From domain.
- Ignoring forwarding: forwarded messages can behave differently under SPF. DKIM and aligned DMARC configuration are especially important for reliable authentication.
- Testing only one recipient: compare results across personal, business, and provider-hosted mailboxes because filtering decisions vary.
If messages bounce, check MX and recipient-account status first. If messages send but land in spam, inspect SPF, DKIM, DMARC alignment, message content, sending reputation, and bounce history. Change one variable at a time and preserve the test results.
When to revisit
Use this checklist again whenever the underlying email workflow changes. Review it before seasonal planning cycles, major campaigns, website launches, domain transfers, DNS migrations, or a move to new cloud hosting.
One-page maintenance checklist
- Monthly: review DMARC aggregate reports, investigate unfamiliar senders, and confirm that important mail passes authentication.
- After adding a service: update SPF, publish the service's DKIM records, test a real message, and document the change.
- After removing a service: remove obsolete SPF includes and DKIM records after confirming that no workflow still depends on them.
- Periodically: review DKIM key-rotation guidance from each provider and rotate keys according to its supported process.
- After DNS or hosting changes: rerun MX, SPF, DKIM, and DMARC lookups and verify website forms separately.
- After a deliverability incident: save bounce messages, authentication headers, DNS results, and timestamps before changing records.
Keep the final configuration in a shared, access-controlled document with the domain owner, DNS host, mailbox provider, sending services, selectors, record purpose, and last review date. For related domain ownership and renewal controls, see the domain portfolio management checklist. A documented baseline turns future email changes from guesswork into a repeatable DNS management task.