• 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!
  • 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.

Full server migration to new server with same hostname?

Chris1

Regular Pleskian
Hello,

I'm wondering whether it is possible to perform a full server migration to a new Plesk server with the same hostname or will Plesk give an error about the hostname being the same?

The new server would not be accessible by hostname (only via IP) until DNS and glue records were changed after the migration.

Would there be any problems with this?

Kind regards,
Chris
 
I think that there are shouldn't be problems with migration if this hostname is not resolvable on destination server. You can try at least.
But why you can't change hostname to production after successful migration?
 
Back
Top