Quick question about multi-site setups and dedicated IPs

Events happening in the community are now at Drupal community events on www.drupal.org.
jamesrgaede's picture

I've seen in various places that having different dedicated IPs for separate domains in a drupal multi-site config is difficult/not possible. My question is, is this really the case and is there any place where I can find a lengthy discussion of it? If not, could some one please explain it like i'm five for me?

I have a multi-site installation in Drupal 7 on a vps with two dedicated IP addresses. I'd like to configure one of the domains I am hosting to use one of the dedicated addresses exclusively, but it is not the primary site (i.e., it's located in the 'sites' folder under its domain name). The purpose would be mainly to have an ssl certificate for that domain (a shared certificate is not an option). Am I out of luck?

Thanks,
James

Comments

I think this would be

Garrett Albright's picture

I think this would be something more sanely configured at the DNS level, far away from the Drupal level. In other words, you'd configure the DNS to route requests for example.com through IP address A, and example.org through IP address B. Then configure your web daemon to respond to both IP addresses. Assuming you have all this working, then Drupal doesn't really need to care what IP address is being used.

But maybe I'm misunderstanding what you're trying to do. Where have you seen it said that it's difficult to do?

Hi Garrett, thanks for the

jamesrgaede's picture

Hi Garrett, thanks for the reply...

My impression is that it is more challenging than this -- if I want a private SSL certificate for the domain with the dedicated IP. Here is what I'm going off of:

http://drupal.org/node/1016590

My interpretation of this is that SSL IP verification takes place at an earlier stage in the domain resolution (wrong word?) process, and since sites share the same code base, I can't assign a dedicated IP to one of the domains in the sites folder. Ideally, I'd like to configure dedicated IP's for each of my sites so that I can utilize gmail as an email return channel, eg:

http://book.civicrm.org/user/current/initial-set-up/email-system-configu...

CiviCRM doesn't support shared SSL, so unless there is some way to accomplish what I'm after here, I think I'll have to use the primary domain as some sort of shared mail resource for the other domains.

Set up your DNS to point to

Slovak's picture

Set up your DNS to point to the respective IPs. Make sure the server is set up for the relevant IPs. In your apache/nginx config is where you determine where to point each SSL connection - and you can point both to the multisite root.

jamesrgaede, you're right

Garrett Albright's picture

jamesrgaede, you're right that you "can't assign a dedicated IP to one of the domains in the sites folder," but simply because Drupal's multisite features work on the basis of the domain name and don't care about IP addresses. All you have to do is what Slovak and I suggested above; configure your DNS server to map each domain to its IP address, then configure your web server to serve both domains from the same Drupal install. The rest should take care of itself.

Thanks for the help

jamesrgaede's picture

Thanks for the help everybody. Just to be clear, mapping IP addresses in DNS is enough for private SSL certificates for each domain?

Cheers
James

Correct.

Slovak's picture

Correct.

This sounds like what I'm looking to do.

billp44ruby's picture

I've got a microsite-based educational content site that I'll license to multiple customers. Each will have their own individual microsite. I had originally thought that domain masking would be the way to go here, but it seems that if I have my customer setup a sub-domain (i.e., microsite.mycustomerdomain.com) and then have them point that sub-domain in their DNS server to my IP address, all I'll need to do is to have a multisite implementation using microsite.mycustomerdomain.com as the site name.

Is it that simple?

It should be that simple, at

Garrett Albright's picture

It should be that simple, at least theoretically, yes. Of course, going to less technically-inclined clients and telling them "yeah, you need to configure your DNS server to point the IP address of the subdomain to my web server" is going to be a stumbling block, but if they can grep that, you should be on your way.

Multisite

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: