How to update dns records without stopping email delivery
Summary
This guide helps you troubleshoot and resolve: How to update dns records without stopping email delivery. Follow the steps below to fix the issue.
Common Causes
Overview
Changing DNS records to point your website to a new server or hosting environment can unintentionally interrupt business email delivery if MX records are not correctly preserved or propagated. This article explains how DNS changes affect email routing, why it is important to verify MX records before and after making web hosting changes, and how to check that messages continue to reach mailboxes during a transition.
Before you begin
Identify where your DNS is hosted
Before making any changes, you must confirm where your domain's DNS records are managed. DNS is not always hosted at the same place where you registered your domain.
- Domain registrar: If you never changed your nameservers, your DNS records are likely managed by the company where you purchased your domain.
- Separate DNS provider: If you use a dedicated DNS service, log in to that provider's control panel to manage records.
- Web host: If your web host manages your DNS, you will make changes inside your hosting control panel rather than at your registrar.
If you are unsure, check your domain's nameserver records using an online lookup tool or contact your domain registrar for confirmation.
Lower the TTL before making changes
At least 24 hours before you plan to make DNS changes, lower the Time to Live (TTL) value on your existing records to 300 seconds (5 minutes). This reduces propagation time and minimises the risk of email disruption during the transition. Remember to raise the TTL back to a higher value after your changes have propagated.
Document your existing MX records
Before changing anything, write down or screenshot every MX record currently listed for your domain. Note the following details for each record:
- Host or name (usually
@or your domain name) - Priority value
- Points to or value (the mail server address)
- TTL (time to live)
An example of a correct MX record is:
- Type:
MX - Host:
@ - Priority:
10 - Points to:
mail.example.com
If you use Microsoft 365, Google Workspace, or another business email suite, these records are critical. Overwriting them will stop email delivery even if your website loads correctly.
@ or example.com) while MX records exist. A CNAME at the root conflicts with MX records and can break email delivery. This is an RFC violation and should be avoided.Update your website DNS record
- Log in to your DNS management control panel. Look for a section labelled DNS Management, Zone Editor, or Manage DNS.
- Select the domain you want to update.
- Locate the
Arecord orCNAMErecord for your website (wwwor the root domain@). - If your new hosting provider gave you an IP address, update the
Arecord to point to that address. Example:
- Type:
A - Host:
@ - Points to:
203.0.113.50
- If your provider gave you a domain name instead of an IP address, update the
CNAMErecord forwwwonly. - Leave all MX records untouched unless you are also migrating your email service to a new provider.
- Click Save, Update, or Add Record depending on your control panel. Some panels require confirmation via email or two-factor authentication.
Verify MX record propagation
Using online tools
Use a free online DNS lookup tool such as MXToolbox or Google Admin Toolbox. Enter your domain and select the MX record type to confirm that your mail server addresses and priority values are still correct and visible globally.
Using command line
On Windows, open Command Prompt and run:
nslookup -type=MX example.com
On macOS or Linux, open Terminal and run:
dig MX example.com
Review the output to ensure the MX records match the values you documented before the change.
Check email delivery after the change
Send a test email to an address on your domain from an external account, such as Gmail or Outlook.com. Reply to the message to confirm two-way delivery. Ask a colleague or staff member to do the same from a different network.
Troubleshooting email delivery failure
Revert DNS changes
If email stops working after your DNS update, immediately restore the MX records to the values you documented before the change. If you also changed the website A record and suspect it caused the issue, revert that record to the previous IP address as well. Save the changes and allow time for propagation.
Check bounce messages and email queues
Review any bounce messages or non-delivery reports received by senders. These messages often indicate whether the failure is due to incorrect MX records, SPF alignment, or mail server rejection. Check your email queue if you manage your own mail server to see if messages are deferred or stuck.
Confirm SPF and DKIM alignment
If you changed your web server's IP address, review your SPF TXT record to ensure it still authorises the correct mail servers. SPF and DKIM records are not automatically updated when you change a website IP address. If outgoing email is landing in spam, verify that your SPF record includes the correct mail server hosts or IP addresses and that DKIM signatures are still valid for your email provider.
When to get help
If you are unsure which records control your email, if your registrar and DNS host are different providers, or if you are moving both your website and email to new providers at the same time, request assistance. Incorrect MX or SPF records can cause outgoing email to be marked as spam or incoming email to be rejected entirely.
If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.
Still Having Issues?
💻 Open a Ticket