[ Date Index ]
[ Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
[LUG] Apache DNS an resolving both externally and internally
Hello all,
At one of the schools I support we have a Mandrake Linux box setup as our intra/internet server running apache.
The background:
We have an internal DNS (2k Active Directory), and an external DIY DNS, all this works fine.
Our gateway port-forwards http traffic to our web server, and https traffic to our email server. all this works fine, but the gateway might not be up to the task of resolving an external ip internally (I get the router logon screen)?
Our intranet and website are hosted on the same apache/mandrake box. Right now, our website is not yet public. They resolve internally by typing 172.30.x.x/subdomain. This I am going to change to virtual hosts.
When I enable virtual hosting all is fine internally. The port forward seems to not work when I have virtual hosting on, in that the webmail server (https) is not accessable, instead http traffic appears (our website).
Our joomla website does not like to resolve to more than one IP/Name on one NIC (I can resolve to one or the other, but resolving to both ends up with one not showing images - I've been all through the joomla forums and the closest I came to a solution is modifying the local host files on each internal client). After I would do this, I would get our gateway router logon screen, and not the actual site.
The options:
I don't know what the best solution to my problem is, or how to go about it exactly. Do I give the linux box a public IP and adjust the DNS host record? Add another NIC and reconfigure? Am I making things difficult on myself? A second box is out of the question/budget.
