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

Plesk IP migration issue

M

MachiM

Guest
Hello,

I will need to change the IP address of several Plesk containers. I
understand how to change the IP in Plesk and also understand how to
bulk change IP address for all domains by following the
KB:http://kb.odin.com/en/943

However there seems to be a problem with the apache configuration,
example as below.

OLD shared IP : 1.1.1.1
NEW shared IP : 2.2.2.2
domain.com : OLD shared IP : 1.1.1.1

Apache is only listening on IP 1.1.1.1 for domain.com. Now if add the
IP address 2.2.2.2 to the server and change the IP address of the
domain to the new IP 2.2.2.2 then the website is no longer accessable
until the DNS change propagates which usually takes upto 48hrs.

This downtime of upto 48hrs is not acceptable. How can I enable
apache to listen on ALL IP address for domain.com ? If apache can
service the site domain.com on both NEW and OLD IP addresses then
during the DNS propagation the webiste will not be down and after
48hrs I can remove the OLD IP.

Basically I am trying to acheive zero downtime when changing IP
address on the same server. Both old and new IP addresses can be
available simultanoesly on the server during the migration process.

I also understand that I can change the DNS TTL to some very short in
order to minimize this, however please note that some domains have
DNS hosted at 3rd party and so it will be very difficult to
arrange/co-ordinate this.

Please advise.

Thanks
 
I would like to know how to do this too. Changing IP within the same server should be something simple to do without downtime.
 
Back
Top