Add MX Records in Netlify | MX Record Checker

Netlify is primarily a web hosting and deployment platform, but it also offers DNS management. If you are using Netlify DNS for your domain, you can add MX records directly through their dashboard to route email to your preferred provider: Google Workspace, Microsoft 365, Zoho, or any other email service.

This guide covers the full process: accessing Netlify's DNS panel, adding MX records, verifying the setup, and understanding when Netlify DNS might not be the best choice for email.

Before You Start

Confirm that your domain is actually using Netlify DNS. If you registered your domain elsewhere and only pointed it to Netlify for web hosting (using a CNAME or A record), your DNS is still managed at your registrar, not at Netlify.

To check: look at your domain's nameservers. If they are Netlify's nameservers (something like dns1.p01.nsone.net through dns4.p01.nsone.net), then your DNS is managed through Netlify and this guide applies. If your nameservers point elsewhere, you need to add MX records at that provider instead.

You will also need the MX record values from your email provider (the mail server hostname(s) and priority number(s)). Have these ready before you start.

Accessing Netlify DNS

Log into your Netlify account at app.netlify.com
Click Domains in the top navigation bar
Find your domain in the list and click on it
You will see the DNS records panel showing all records for your domain

Netlify's DNS interface is straightforward. Records are listed in a table, and you can add, edit, or delete records from this page.

Removing Old MX Records

If your domain has existing MX records (whether from a previous email provider or from any default configuration), remove them before adding new ones. Conflicting MX records cause unpredictable email delivery, with messages randomly going to different servers.

In the DNS records list, find any records with type MX
Click the Options menu (three dots) next to each MX record
Select Delete and confirm

Once all old MX records are removed, you are ready to add fresh ones.

Adding MX Records

Click the Add new record button
Select MX from the record type dropdown
Fill in the fields:
- Name: Leave blank or enter @ for your root domain (Netlify accepts either)
- Priority: The priority number from your email provider
- Value: The mail server hostname from your email provider
- TTL: Leave at default (3600 is standard)
Click Save
Repeat for each MX record your provider requires

Adding Google Workspace MX Records

Google Workspace requires five MX records. Add each one separately:

Name: (blank)  |  Priority: 1   |  Value: aspmx.l.google.com
Name: (blank)  |  Priority: 5   |  Value: alt1.aspmx.l.google.com
Name: (blank)  |  Priority: 5   |  Value: alt2.aspmx.l.google.com
Name: (blank)  |  Priority: 10  |  Value: alt3.aspmx.l.google.com
Name: (blank)  |  Priority: 10  |  Value: alt4.aspmx.l.google.com

After adding all five, your DNS records list should show five MX entries. The priority 1 server is the primary delivery point, with the others serving as backups.

Adding Microsoft 365 MX Records

Microsoft 365 uses a single MX record unique to your domain:

Name: (blank)  |  Priority: 0  |  Value: yourdomain-com.mail.protection.outlook.com

Replace yourdomain-com with your actual domain name, using hyphens instead of dots. Find the exact value in your Microsoft 365 admin center under Settings > Domains.

Adding Other Email Providers

Common MX record values for popular providers:

Zoho Mail:

Priority: 10  |  Value: mx.zoho.com
Priority: 20  |  Value: mx2.zoho.com
Priority: 50  |  Value: mx3.zoho.com

ProtonMail:

Priority: 10  |  Value: mail.protonmail.ch
Priority: 20  |  Value: mailsec.protonmail.ch

Fastmail:

Priority: 10  |  Value: in1-smtp.messagingengine.com
Priority: 20  |  Value: in2-smtp.messagingengine.com

Always verify the current values in your email provider's setup documentation, as these can change.

Verifying Your MX Records

After saving your records, go to mxrecordchecker.com and enter your domain. The tool will show which MX records are currently live. Netlify DNS changes typically propagate within a few minutes, though full global propagation can take up to 48 hours.

If you see your new records with the correct mail server hostnames and priorities, the configuration is working. If the old records still appear, wait 15-30 minutes and check again.

Send a test email from an external account (a personal Gmail or Outlook address) to your business email address. If it arrives, your MX records are routing email correctly.

Limitations of Netlify DNS for Email

Netlify DNS works fine for basic MX record management, but there are some limitations worth knowing about:

No email-specific features. Unlike Cloudflare (which offers email routing and forwarding), Netlify DNS is a basic DNS service. It hosts your records and serves them, nothing more. If you need email forwarding or catch-all functionality at the DNS level, you will need to handle that through your email provider.

No DNSSEC support. As of this writing, Netlify DNS does not support DNSSEC (DNS Security Extensions). For most small businesses, this is not a dealbreaker, but if your organization requires DNSSEC for compliance or security reasons, you will need a different DNS provider.

Limited record types. Netlify supports the most common DNS record types (A, AAAA, CNAME, MX, TXT, NS), which is sufficient for email setup. However, some advanced configurations might require record types that Netlify does not support.

No API for DNS management. If you manage DNS programmatically or need to automate record changes, Netlify's DNS does not offer an API for this. Providers like Cloudflare or AWS Route 53 are better suited for automated workflows.

Primarily designed for web hosting. Netlify built their DNS service to complement their web hosting platform. Email DNS management works, but it is not their core focus. If email reliability is critical to your business, consider whether a dedicated DNS provider might be a better fit.

When to Use External DNS Instead

For many Netlify users, it makes more sense to manage DNS at a dedicated provider and just point your domain to Netlify for web hosting. Here are scenarios where external DNS is the better choice:

You need advanced DNS features. If you want email routing, DNSSEC, geographic DNS, or weighted routing, use a provider like Cloudflare or AWS Route 53.

You manage multiple services. If your domain needs complex DNS configurations for email, web hosting, subdomains, and other services, a full-featured DNS provider gives you more control and better tooling.

You want faster support for DNS issues. DNS problems can take your email offline. Having DNS managed at a provider whose primary business is DNS means faster support resolution.

You are a developer using Netlify for deployments only. You can still deploy to Netlify using a CNAME record from another DNS provider. You do not need Netlify DNS to use Netlify hosting.

If you decide to move DNS away from Netlify, update your nameservers at your domain registrar to point to your new DNS provider, and recreate all your records (including MX records) there.

Troubleshooting Common Issues

MX records not showing up. Verify you saved each record after filling in the fields. Check that you selected MX as the record type, not TXT or CNAME. Confirm your domain is actually using Netlify's nameservers.

Email bouncing after adding records. Double-check the mail server hostname for typos. Make sure the priority values match what your email provider specifies. Confirm that the destination mailbox exists at your email provider.

Records visible in Netlify but not in external lookups. DNS propagation may still be in progress. Netlify DNS changes usually appear quickly, but cached records at other resolvers may take longer to expire. Wait an hour and check again at mxrecordchecker.com.

Website works but email does not. Website hosting and email are separate systems. Your site being live on Netlify has no bearing on email delivery. That depends entirely on MX records pointing to the right mail server.

Additional Records for Email

MX records handle incoming email routing, but a complete email setup also includes authentication records:

SPF record: A TXT record that authorizes your email provider to send from your domain. Check yours at spfrecordcheck.com.

DKIM record: A TXT or CNAME record that adds a cryptographic signature to outgoing email. Your email provider generates this. Verify at dkimtest.com.

DMARC record: A TXT record that defines what happens when email fails authentication checks. Check at dmarcrecordchecker.com.

Add these after your MX records are working correctly. Getting email flowing first, then adding authentication, makes troubleshooting easier.

How to Add MX Records in Netlify DNS - Step-by-Step Guide