How to ensure no downtime for email traffic when transferring DNS from current webhost to Cloudflare
We're switching our domain names from the current web host to Cloudflare and our main concern is the email traffic.
The main key findings I've found so far are:
1) Always proxy A records. CNAME records should be proxied if they are serving HTTP/S traffic. If not, do not proxy CNAME records.
2) Never proxy email traffic as it goes through a different port than HTTP/S traffic.
3) Copy existing DNS records down to a T from the previous web host
4) Update the name servers preferably when the traffic is the lowest (aka evening / night time / weekend)
5) Test sending and receiving emails after the update has been successful.
But is there something crucial or anything else I should take into account? And if I've misunderstood some of the concepts, please feel free to correct me 🙏
3 Replies
Support AI
Your key findings are mostly correct. However, I'd like to clarify and add a few points to ensure a smooth transition.
1. Proxying A records and CNAME records: You're correct that A records should always be proxied, and CNAME records should be proxied if they serve HTTP/S traffic. However, it's essential to note that some CNAME records might not be proxied, such as those used for email or other non-HTTP/S services.
2. Email traffic: You're correct that email traffic should not be proxied, as it uses different ports (e.g., SMTP, IMAP, and POP3). Make sure to keep the MX records (which route email traffic) unproxied.
3. Copying existing DNS records: It's crucial to copy the existing DNS records accurately, including the TTL (Time To Live) values. This ensures that the DNS resolution process works correctly during and after the transition.
4. Updating name servers: Updating the name servers during low-traffic periods is a good practice. However, it's also important to ensure that the DNS changes propagate globally before making the switch. You can use tools like DNSChecker or WhatsMyDNS to verify the propagation.
5. Testing email functionality: After updating the name servers, test sending and receiving emails to ensure that email traffic is working correctly.
Additional considerations:
* MX record configuration: Verify that the MX records are correctly configured and point to the correct mail servers. You can use the Cloudflare DNS manager to configure MX records.
* SPF, DKIM, and DMARC records: If you're using SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), or DMARC (Domain-based Message Authentication, Reporting, and Conformance) records, ensure they are correctly configured and updated during the transition.
* Mail server configuration: If you're using a third-party mail service, verify that their configuration is compatible with Cloudflare's DNS setup.
* Monitoring and troubleshooting: Keep an eye on your email traffic and DNS resolution during the transition. Use tools like Cloudflare's DNS analytics and email logs to troubleshoot any issues that may arise.
To confirm, you can refer to Cloudflare's documentation on configuring DNS records for email and troubleshooting email issues.
If you have any further questions or concerns, feel free to ask! 😊
Sources
This is an AI generated response, it may not be 100% accurate. Please validate the output. You can ask followups by replying to this message or mentioning me.
is your email provider changing too?
if not you should not experience any downtime
the 72 hour period of dns change is just updating cache for clients who don't respect TTLs
also dont worry too much about changing servers when traffic is low, as long as your a records are the same you should be fine
The email provider will stay the same.
Also thanks a bunch for the encouragement ❤️ 💪