• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question DNS: How to configure MX for server change

speedbird

Basic Pleskian
Alright dear pleskians, I do need help – or clarification to be precise ;)

What I want to do is to move accounts from my current plesk server to a new plesk server without causing any issues for the mail users.

So current setup is as follows:

Current MX record: mail.currentdomain.com

All users use this domain, which is SSL secured, to connect to the mailserver.

I plan on setting up a second plesk server where these accounts will be moved to.

New server MX record: liam.newdomain.com

Now... How can I achieve it per DNS to redirect users to the new server without them having to make any changes to their configuration or their mail client throwing error because of wrong certs?

My idea so far was to create a CNAME which basically redirects mail.currentdomain.com to liam.newdomain.com but I'm not quite sure if that's the way to go.

So I need your help. How can every user still use mail.currentdomain.com in their mail programms but is redirected without any trouble to the new server because it's going to be a mess if everybody needs to adjust their accounts on every freaking device they own.

Thanks :)
 
That only works if the new server knows it's supposed to answer to and has the cert for mail.currentdomain.com.
Much easier to set up plesk with the same old domain name and switch DNS over at some point. You'll need to copy the certs from the old to the new server though.
 
What mow said. Set the the TTL of the domain very low, like 5 minutes, wait 24 hours so it propagated everywhere and switch to the new server.
 
Back
Top