Propagation

MX Record Propagation — How Long It Takes

MX record changes take 1-4 hours on average. Email delivery uses the old server until propagation completes — here's how to minimise disruption.

Email during propagation

MX is cached like any record. Senders don't all flip at once — that's normal. Good providers queue and retry.

Lower TTL before the change. After everyone sees the new MX, you can raise TTL again for stability.

Check MX propagation

Also read: MX record setup guide

Step 1 If your DNS host allows it, drop TTL a day before the migration.

Step 2 Replace MX records with your provider's exact hostnames and priorities.

Step 3 Use Propagation checker with type MX and your apex domain.

Step 4 Ensure every resolver lists the same mail hosts and preference order.

Step 5 Senders may still use cached MX briefly — most queues retry automatically.

Often one to four hours; worst case up to 48 hours if TTLs were high or NS paths are involved.

Sending servers cache MX. Until their cache expires, they may deliver to the previous mail infrastructure — queues usually retry.

Yes — lower TTL first so resolver caches refresh faster after you publish new MX records.

DomainPreflight Propagation — select MX, enter your domain, wait until all five resolvers match.

Residual cache. Verify authoritative DNS, wait for TTL, check Propagation again — most stragglers clear within hours.