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

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