• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question about assigning an exclusive IP

J

JerkyChew

Guest
Hi,

We are running a Plesk 7.5 box with several domains on a shared IP. A couple clients would like secure sites, so I have procured the IP addresses needed for each domain. However, I have a question before I change the status of the exclusive IP.

The plan is to log into the server, go to IP addresses, click the 0 under clients, and add a client to that IP address. If I do that, will the IP change happen immediately? Do I need to do anything else so that www.blah.com now points to that IP? Of course if it's immediate I'd like to know that, as I'm sure it would break some of their site till DNS propogates across the net.
 
Ok, more info. I've found that I can add the client, but I don't have to add the IP until afterwards. I go to the setup for that domain, hosting, and change the default IP address via the drop-down box. But that still doesn't answer my question - When I change that pulldown, will that modify all the DNS and IP info on the domain, causing some people to get a broken page until the DNS propogates?
 
Umm,

When you set the Default IP it will only list the domains which are currently ON that IP. When you change the IP for the domain to the dedicated IP, yes, it will break the site.

TO avoid that, change to the dedicated IP then added this to the bottom of your httpd.conf:

1.2.3.4 is the -> OLD <- IP

Code:
<VirtualHost 1.2.3.4:80>
ServerName [url]www.clientsdomain.com[/url]
ServerAlias clientsdomain.com

ProxyPreserveHost On
ProxyPass / [url]http://www.clientsdomain.com/[/url]
ProxyPassReverse / [url]http://www.clientsdomain.com/[/url]
</VirtualHost>

Then restart Apache. What that effectively does is force Apache to proxy requests for that domain on the old IP to the IP the domain currently resolves to (based on DNS lookup results). Since it's just another IP on the box it'll proxy to itself (ie. serving the same site on 2 IPs).

After the DNS cache has been flushed (72hrs or so) nuke those lines and the transition is complete.

Stuart
 
WOW THIS FIXED MY PROBLEM, THANKS!!!!

(I moved a domain to another IP and it was not working, this fixed it!)

-zboyblue
 
Back
Top