View Single Post
  #8  
Old 13th March 2012, 17:40
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 34,573
Thanks: 792
Thanked 4,980 Times in 3,901 Posts
Default

Quote:
Originally Posted by desanidesigns View Post
I did see that in the roadmap. I believe what I ran into before is that when I selected the * for a domain, it messed with sites that didn't have the * and would show the wrong site. Say I went to www.a.com, it would show www.b.com.
The problem is that a IP address is priorized in favor of a wildcard by apache. But this can be avoided by the correct IP setup:

1) Create a "fake" client account and assign it the "main" ip which is internally used for all sites with *. So there is no site where this IP address is selected directly,all sites that point in DNS to this IP use * instead.

2) All websites that dont use SSL use *. The clients have no other choice then using * as there are no other IP's active on the server 'globally' and the only other IP is assigned to the fake client.

3) If you add a ssl site that requires a separate IP, add this new ip under system > Server IP and assign it to the client that owns this sl site. So this IP will only show up for him and no other customers.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote