Home › Knowledgebase › KB-1157

Preventing Website Email Outages When Updating Your DNS Records

Summary

This guide helps you troubleshoot and resolve: Preventing Website Email Outages When Updating Your DNS Records. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Detailed Instructions

Updating your domain's DNS records is often necessary when migrating your website, changing hosting providers, or verifying ownership of a third-party service. However, because your email delivery relies on specific DNS entries—specifically MX records—an incorrect change can cause your business email to stop arriving or prevent your emails from being delivered to clients. This guide walks you through how to update your DNS records safely without disrupting your email service.

1. Lower Your TTL Values Before Making Changes

Warning: Lower your Time to Live (TTL) values at least 24 to 48 hours before making any DNS changes. If you change records while the TTL is still set to a high value (such as 86400 seconds), the changes will propagate slowly, and your email may experience extended downtime or delivery failures while caches expire.

Before making any DNS changes, lower the Time to Live (TTL) value on your records to a short interval, such as 300 seconds (5 minutes). This ensures changes propagate quickly and reduces the window for potential email outages.

  1. Log in to your domain registrar or DNS management portal.
  2. Navigate to the DNS Management or Zone Editor section.
  3. Locate your existing records and change the TTL to 300 seconds.
  4. Save the changes and wait for the current TTL period to expire before proceeding.

Common Control Panel Paths

2. Backup Your Current DNS Records

Before changing any settings, take a screenshot or export a list of your current DNS zone file. This ensures you can revert to a working configuration if email delivery stops.

  1. Log in to your domain registrar or DNS management portal.
  2. Navigate to the DNS Management or Zone Editor section.
  3. Locate your MX records. Note the priority value and the mail server address (for example, mail.example.com or aspmx.l.google.com).
  4. Save these details in a secure document.

3. Verify Your Email Provider MX Records Before Deleting Anything

Before deleting or modifying any MX records, confirm the correct values with your email provider. Deleting the wrong record will stop incoming email immediately.

Common Email Provider MX Record Examples

Provider MX Record / Mail Server Priority
Microsoft 365 example-com.mail.protection.outlook.com 0
Google Workspace aspmx.l.google.com 1
Google Workspace (backup) alt1.aspmx.l.google.com 5

Replace example-com with your actual Microsoft 365 tenant domain prefix. If you use Telstra, Optus, or another Australian ISP for email, contact their support or check their help centre for the exact MX values before making changes.

Caution: Deleting an MX record will stop incoming email immediately. Do not remove these records unless you have a replacement email routing plan ready. Expect email downtime during MX record propagation, which can take up to 48 hours.

4. Update Your Records Carefully

When updating records for a new website or server, avoid deleting your MX records unless you are intentionally moving your email service to a new provider.

  1. Click Add Record or Edit next to the record you wish to change.
  2. If changing your website's IP address, update only the A record for your root domain (@) and your www subdomain.
  3. Leave your MX records untouched unless you are also migrating your email.
  4. Click Save or Update Record to apply the change.

5. Configure Email Authentication (SPF, DKIM, and DMARC)

To prevent your emails from being marked as spam after a DNS change, ensure your SPF, DKIM, and DMARC records are correct.

SPF Record

Add or update your TXT record for SPF at your root domain (@). The record must include every server authorised to send mail for your domain. An invalid SPF record can cause receiving servers to reject your email.

Example for Google Workspace:

v=spf1 include:_spf.google.com ~all

Example for Microsoft 365:

v=spf1 include:spf.protection.outlook.com ~all

Warning: Do not create multiple SPF TXT records for the same domain. If you use multiple email services, combine them into a single SPF record, such as v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all.

DKIM Record

Ensure your DKIM public key is published as a TXT record. The DNS host name typically follows the format selector._domainkey.yourdomain.com, where selector is the DKIM selector provided by your email provider (for example, default, google, or selector1). Check your email provider's admin console for the exact host name and value.

DMARC Record

Consider adding a DMARC record to tell receiving servers how to handle authentication failures. Create a TXT record at the host name _dmarc.yourdomain.com.

Example DMARC record:

v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com

Replace example.com with your actual domain. Start with p=none if you want to monitor reports without affecting delivery, then move to p=quarantine or p=reject once you have confirmed your SPF and DKIM are working correctly.

Troubleshooting

Email is not arriving after a DNS update

  1. Check that your MX records still point to the correct mail server.
  2. Verify that the priority numbers are set correctly (lower numbers have higher priority).
  3. Use a DNS lookup tool to confirm that the changes have propagated globally.
  4. Check your email provider's admin console for any delivery errors or bounce messages.

How to Verify DNS Propagation

  1. Open Google Admin Toolbox Dig (toolbox.googleapps.com/apps/dig/) or MXToolbox (mxtoolbox.com/DNSLookup.aspx).
  2. Enter your domain name and select MX or TXT from the record type dropdown.
  3. Review the results to confirm your records are visible across multiple nameservers.
  4. If the records do not appear, wait and check again. DNS propagation can take anywhere from a few minutes to 48 hours.

Emails are being marked as spam

  1. Analyse your SPF record to ensure it includes all servers authorised to send mail for your domain.
  2. Verify that your DKIM signature is active and matching.
  3. Wait 24–48 hours for full DNS propagation across Australian and international ISPs.
  4. Use MXToolbox or Google Admin Toolbox to check that your SPF, DKIM, and DMARC records are valid.

Note: DNS changes can take anywhere from a few minutes to 48 hours to update across all servers worldwide. Avoid making multiple changes in quick succession, as this makes it harder to identify which change caused an issue.

If you have followed these steps and are still experiencing email delivery issues, you can Open a Ticket with our Brisbane support team.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket