iCloud Custom Domain MX Records Complete Setup and Troubleshooting Guide

Setting up a custom domain with iCloud Mail sounds straightforward until you hit the DNS configuration step and realize Apple expects very specific MX record values in a very specific format. Miss one detail and your email either bounces entirely or keeps landing in a fallback mailbox nobody checks. This guide covers exactly what MX records iCloud requires, how to enter them at every major registrar and hosting provider, how to verify the records are working, and how to recover if something has already gone wrong.

What iCloud Custom Domain Email Actually Is

Apple's iCloud Mail with a custom domain lets you send and receive email at your own address, such as you@yourdomain.com, through the iCloud Mail infrastructure. It is part of iCloud+ (the paid subscription tier). You manage the domain you already own, Apple handles the mail servers. The feature supports up to five custom domains on a single iCloud+ account, and each domain can have addresses assigned to family sharing members.

The MX records tell the internet which mail servers are responsible for accepting messages sent to your domain. Without correct MX records pointing at Apple's servers, any email someone sends you will be rejected or routed to the wrong place entirely.

The Exact MX Records Apple Requires

Apple specifies two MX records for iCloud custom domain email. These values are the same regardless of which domain registrar or DNS host you use:

A few things to note before you enter these anywhere:

• The trailing dot after .com is standard DNS notation. Most control panels add it automatically. If your registrar's interface shows a plain text field with no trailing dot, just type mx01.mail.icloud.com without the dot and the system will handle it.
• Priority numbers matter. 10 is the primary server. 20 is the fallback. Some panels label this field "Priority," others call it "Preference" or "MX Preference." It is the same thing.
• The host field for both records should be @ (meaning the root domain) or left blank, depending on the registrar. This is the most common source of mistakes.
• TTL can be left at your registrar's default (usually 3600 seconds / 1 hour). Lower it to 300 temporarily if you need faster propagation during a cutover.

Required Supporting Records: SPF, DKIM, and CNAME

MX records alone are not enough. Apple also requires you to add an SPF record and a DKIM CNAME record before iCloud will fully activate the domain. Without these, email delivery is unreliable and iCloud's setup wizard will show a persistent warning.

SPF Record

Add a TXT record at the root of your domain (@) with this value:

If you already have an SPF record for another mail service (Google Workspace, Mailchimp, etc.), merge them into a single TXT record. You cannot have two separate SPF records on the same host. For example:

DKIM Record

Apple generates a unique DKIM CNAME record for your specific domain during the setup wizard. It looks like this format but the left side will be unique to you:

Copy the exact values shown in your iCloud Settings rather than using a generic example. The subdomain prefix (the part before ._domainkey) is generated per-domain.

How to Add the Records at Major Registrars

GoDaddy

1. Log in and go to My Products, then click DNS next to your domain.
2. Scroll to the MX section. Delete any existing MX records that point to GoDaddy's own mail servers (they add placeholder records by default).
3. Click Add. Type: @, Value: mx01.mail.icloud.com, Priority: 10, TTL: 1 hour.
4. Add a second record: @, Value: mx02.mail.icloud.com, Priority: 20.
5. Save both records and add the SPF TXT and DKIM CNAME records the same way.

Namecheap

1. Go to Domain List, click Manage, then select the Advanced DNS tab.
2. Under Mail Settings, switch the dropdown from "Namecheap Email Forwarding" or any current option to Custom MX. This reveals the MX record fields.
3. Enter @ as the host, the two mail server values at priorities 10 and 20.
4. Add your TXT (SPF) and CNAME (DKIM) records in the Host Records section below.

Cloudflare

1. In the Cloudflare dashboard, select your domain and go to DNS > Records.
2. Click Add record. Set type to MX, name to @, mail server to mx01.mail.icloud.com, priority to 10.
3. Add a second MX record for mx02.mail.icloud.com at priority 20.
4. MX records in Cloudflare are automatically set to DNS-only (grey cloud). This is correct — do not proxy MX records.
5. Add the TXT record for SPF and the CNAME for DKIM. For the DKIM CNAME, make sure it is also set to DNS-only, not proxied.

Google Domains (now Squarespace Domains)

1. Open your domain's DNS settings and find the Custom records section.
2. Add an MX record with host @, TTL 3600, data 10 mx01.mail.icloud.com.
3. Add a second MX: 20 mx02.mail.icloud.com.
4. Google's interface combines the priority and hostname in a single data field, so enter the priority number followed by a space before the mail server name.

Verifying Your MX Records Are Live

Once you have saved the records, verify them from the command line rather than trusting the registrar's own dashboard, which may show cached or pre-save values.

Expected output should show both Apple mail servers with their priorities:

If you see your old MX records or no records at all, propagation is still in progress. Wait 15 to 30 minutes and run the command again. You can also use the DNS Lookup tool to query MX records from multiple vantage points at once without installing any software.

Common Problems and How to Fix Them

iCloud Settings Still Shows "Action Required" After Adding Records

Apple's verification checks run on a schedule, not instantly. After propagation looks complete from your own tests, go back to Settings > iCloud > iCloud Mail > Custom Email Domain, select your domain, and tap or click the verification button. If it still fails, the most likely causes are:

• The host field is set to yourdomain.com instead of @. This creates a record at yourdomain.com.yourdomain.com, which is wrong.
• Your registrar has a separate "email forwarding" service that overrides custom MX records. Disable it before saving your Apple records.
• A wildcard MX record exists that takes priority. Check for any existing MX entries and remove them.

Email Bouncing With "550 No such user" or Similar Errors

The MX records are working, but the address is not properly claimed in iCloud. Go to iCloud Settings > Custom Email Domain and confirm the specific address (e.g., you@yourdomain.com) is listed and active. Each person using the domain must be added individually inside iCloud's custom domain management screen.

Sent Mail Being Marked as Spam by Recipients

Your MX records are fine but your SPF or DKIM record is missing or misconfigured. Run an SPF check by querying the TXT records for your domain:

Confirm you see a record beginning with v=spf1 that includes include:icloud.com. Then check the DKIM CNAME:

It should return a CNAME pointing to sig1.dkim.icloud.com.

Existing Email Service Stopped Working After Adding Apple's Records

You replaced your previous provider's MX records with Apple's without migrating first. MX records are all-or-nothing for a domain — all incoming mail goes to whichever server the MX records point to. If you need to run two mail services on the same domain simultaneously, that is generally not supported. You need to choose one provider for receiving mail and use forwarding or aliases for the other addresses.

How to Test End-to-End Email Delivery

After verification succeeds in iCloud Settings, send a test from an external address (Gmail, Outlook, a friend's account) to your custom domain address. Check that it arrives in iCloud Mail on the web at icloud.com or in the Mail app. Then reply and confirm the reply comes from your custom domain address, not from an @icloud.com address. If replies still show the @icloud.com address, check that iCloud Mail's default sending address is set to your custom domain under Mail Settings > Account > Alias.

Preventing Future Problems

• Do not let your iCloud+ subscription lapse. Custom domain email is tied to the active subscription. If the subscription expires, email delivery stops and Apple may release the domain configuration.
• Document your DNS records. Keep a local copy of all records — MX, SPF, DKIM CNAME — so you can quickly restore them if you ever migrate DNS hosts or accidentally delete records.
• Avoid using your registrar's built-in email forwarding alongside custom MX. These two features conflict. If you need forwarding for some addresses and iCloud for others on the same domain, manage everything through iCloud's custom domain alias system instead.
• Set a calendar reminder to re-verify DNS records annually. Hosting migrations and registrar changes can silently overwrite DNS records, and problems may not surface until someone tells you they never received an email.
• Use a low TTL (300 seconds) before any planned DNS change, then restore it to 3600 after the change is confirmed working. This shortens the propagation window during transitions.

Summary of All Required DNS Records

Every registrar and DNS host uses slightly different terminology in their control panels, but these four records are what Apple requires. Get these right, wait for propagation, trigger the verification check in iCloud Settings, and your custom domain email will be fully operational. If you run into edge cases around record conflicts or unusual registrar configurations, the command-line verification steps above are the fastest way to confirm exactly what the rest of the internet sees for your domain — not just what your control panel claims to have saved.