System Admin is not my strong point. My situation is we have 1 website that has 4 domains. The website itself serves different templates/content depending on which domain is used, simulating 4 different websites.
We want SSL for each domain (we currently have it all set up properly with apache and it is working on 3 sites).
We have 3 physical network interfaces: eth5, eth6, eth7. A past employee wrote these ip route rules to help setup our virtual host IP addresses. I don't really understand what's going on on these, except that with these in place, 3 of our domains work properly with SSL, corresponding to virtual hosts for each ip address *.95
Eth5 ip route add *.*.*.0/24 dev eth5 proto kernel scope link src *.*.*.95 table 20 ip route add default via *.*.*.1 dev eth5 table 20 ip rule add from *.*.*.95 lookup 20 Eth6 ip route add *.*.*.0/24 dev eth6 proto kernel scope link src *.*.*.12 table 40 ip route add default via *.*.*.1 dev eth6 table 40 ip rule add from *.*.*.12 lookup 40 Eth7 ip route add *.*.*.0/24 dev eth7 proto kernel scope link src *.*.*.11 table 30 ip route add default via *.*.*.1 dev eth7 table 30 ip rule add from *.*.*.11 lookup 30
These rules have worked for 3 of the 4 websites we need SSL. We have another IP address *.14 that we have told our internal (bind9) and godaddy DNS (correlating to the public IP for *.14 which is *.70) to point here. But I feel like I need to be adding another rule.
I want to know what these rules do, why I need a rule, and how I can make .14 actually work.
The domain that I want to point to 14 is pointing to 12 (on our internal site). Externally it is pointing to 70 which is 14 so nothing is showing up, because that part is not working!
Edit to Answer Florenz's comment:
Our server is running Ubuntu 12.10. We have apache that handles our virtual hosts with a folder called sites-available and another sites-enabled. I have that part all working properly, where there are four sites available and enabled, containing virtual hosts.
In those, we have
<virtualhost> that contain the IP addresses that correpsond to .95, .11, .12 and the one not working .14 Since they use SSL, they use the Port:443
All the SSL certs are running and linked in there as well. I don't think that the apache side of the virtual hosts are not done correctly. I think it has to do with these IP Route rules. I don't really know much about this stuff so it's hard to explain it.