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

move ip's on the server (normally for SSL)

ollybee

New Pleskian
I can only have a site configured on one ip at a time.
This is a problem when I have a site configured on a shared ip and I want to move it to a dedicated for use with an SSL.
While the DNS update propagates either I may get requests for the site on either IP, only one of which can work.
I can mitigate this problem by reducing the TTL od the DNS records, if I have control; or making the change at at night.

Is there a better way to move a site to a new ip on the server without any downtime ?
 
I can only have a site configured on one ip at a time.

That is true for Plesk ...

When moving a website from a shared IP, the new server should also have a shared IP and thus a domain is moved from shared to shared IP, while for dedicated IP is must also be moved to a dedicated IP address.
 
Back
Top