• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

2 IPs to 1 domain

D

Dawn

Guest
I've bought a SSL cert for a domain. So that domain needs its own ip address. I've got an ip left. But when I assign the new IP to this domain I've got to change the nameserver entry.

So my question is how can I asign two IP's to a domain? That would be perfect and there wouldn't be any time which isn't the domain (the website) unavailable over the dns name...

I hope anybody can help me with that problem...

Greets and THX anyway,
Dawn
 
I'm looking to do the same, but the other way round to free up IPs; i.e. moving a domain from an exclusive IP to a shared IP, but with zero downtime while the DNS updates.

So I'd like to know if this is possible too.
 
I found a solution.. It's not the best, but it makes your website available.

If you understand german you can read about it here:
http://www.blankster.info/faq/3_19_de.html

I try to explain it in english too, but my english isn't very good ;)

First of all I have to explain that this solution doesn't makes all services (for example mail, ftp....) avaiable over the second IP, but you can reach the website at both IP's.

1. You have to copy your current /var/www/vhosts/domain.com/conf/http.2ndip (I can only give you my debian pathnames) to /var/www/vhosts/domain.com/conf/http.2ndip.

2. Edit http.2ndip and replace all ip adresses with the new ip adress. You have to do that for the HTTP as the HTTPS part.

3. Now you have to edit your /var/apache2/apache2.conf and include at the end the line "Include /var/www/vhosts/domain.com/conf/http.2ndip"

4. If the DNS-entry is pointing to the old ip-adress your website is reachable as normal. If the IP change for the DNS-entry your website is reachable at the new ip.

5. Change the IP as soon as possible in plesk to make all services available. You can check to which IP the DNS-entry points with a "ping domain.com -t".

I hope that helps you. If anybody out there has got a better solution, it would be nice to know it.

Greets,
Dawn
 
Back
Top