Email DNS records control how your domain sends, receives, verifies, and routes email. A small change can affect every mailbox on the domain, so it is worth slowing down before you edit anything.
This is especially true if your business relies on email for leads, quotes, bookings, invoices, customer service, password resets, or vendor communication.
Confirm the Reason for the Change
Start by identifying exactly why the email DNS record needs to change.
Common reasons include:
- Setting up Microsoft 365
- Moving email to a new provider
- Adding SPF, DKIM, or DMARC
- Connecting an email marketing platform
- Fixing messages going to spam
- Changing nameservers
- Rebuilding DNS after a website move
Different goals require different records. Do not update MX records when the task only calls for SPF. Do not remove authentication records when you are only changing website hosting.
Find the Active DNS Provider
Before editing anything, confirm where DNS is live.
The domain registrar is not always the active DNS provider. Nameservers decide which DNS zone is active.
If your domain uses Tech Help Canada Hosting DNS, use the Tech Help Canada Hosting portal to review and manage the domain’s DNS records. If the nameservers point elsewhere, make the DNS change with that provider instead.
Changing records in the wrong account will not affect live email, but it can waste time and create confusion during troubleshooting.
Copy the Current Records
Before you edit records, save the current setup.
Record the existing:
- MX records
- SPF TXT record
- DKIM records
- DMARC TXT record
- Autodiscover records
- Any CNAME or SRV records used by email
- Any verification records for email tools
Screenshots are useful, but copied text is better for long TXT records because a screenshot can hide characters or line wrapping.
Label what each record appears to do. For example, “Microsoft 365 SPF,” “email marketing DKIM,” or “old provider MX.”
Check Who Uses the Domain for Email
Make a list of every address that receives mail at the domain.
Include:
- Staff mailboxes
- Owner mailboxes
- Shared inboxes
- Aliases
- Forwarders
info@,contact@,sales@, andbilling@- Website form recipients
- Booking, invoicing, CRM, or ecommerce addresses
If you move incoming mail before these addresses exist in the new system, messages may fail.
List Every System That Sends Email
Receiving is only part of the setup. Your domain may also send email through several services.
Check for:
- Regular business email
- Website contact forms
- Appointment reminders
- Invoices and receipts
- CRM messages
- Ecommerce order emails
- Email marketing campaigns
- Help desk or ticketing tools
Each sender may need SPF, DKIM, or domain verification records. If you forget one, only some messages may fail or land in spam.
Watch the SPF Record
SPF is commonly misconfigured during DNS edits.
Most domains should have one SPF TXT record at the root domain. If you need to authorize several senders, their SPF instructions usually need to be combined into that one record.
Do not add a second SPF record just because a new provider gives you one. Check the existing record first and follow the provider’s instructions for including multiple senders.
Be Careful With MX Records
MX records control incoming mail delivery. Changing them is a cutover step, not a casual edit.
Before changing MX records:
- Create the new mailboxes
- Confirm aliases and shared mailboxes
- Confirm migration or forwarding plans
- Check whether old mail needs to be moved
- Choose a lower-traffic time
- Tell affected staff what to expect
- Keep the old settings available in case you need to compare them
If your website is moving but email is staying with the same provider, make sure the email MX records are copied into the new DNS zone.
Check DKIM and DMARC Timing
DKIM may require DNS records plus an activation step inside the email provider. Adding the DNS record alone may not finish the setup.
DMARC should usually be introduced carefully. A monitoring policy such as p=none lets you see what is happening before asking receiving systems to quarantine or reject failing mail.
If several services send email for your domain, confirm they are authenticated before moving to stricter DMARC policies.
Plan the Test
After changing email DNS records, test from outside your domain.
Test:
- Receiving from another provider
- Sending to another provider
- Replies
- Website forms
- Invoices or automated emails
- Marketing platform verification
- Spam or junk placement
- Mobile and desktop app access
Keep a short change log with the time, record changed, old value, new value, and reason. This helps if a problem appears hours later.
Do Not Rush a Multi-Part Change
If you are changing nameservers, moving email, and launching a website at the same time, separate the work into steps where possible. It is much easier to troubleshoot one change than five.
For many small businesses, the safest approach is to prepare new records, create mailboxes, document the old setup, make the change during a quieter time, then test immediately.
If your next step is setting up domain-based business email, you can explore Microsoft 365 through Tech Help Canada Hosting.
I can suggest related Tech Help Canada articles based on the topic you’re reading now.
We empower people to succeed through practical business information and essential services. If you’re looking for help with SEO, copywriting, or getting your online presence set up properly, you’re in the right place. If this piece helped, feel free to share it with someone who’d get value from it. Do you need help with something? Contact Us
Want a heads-up once a week whenever a new article drops?
