Internal DNS server needed??

[jme]

Hey guys.

Soon I will have two web servers sat behind my firewall (smoothwall). At the moment things are pretty simple as I just forward any port 80 requests to the one webserver, but when I get the second server I will need to forward different requests to different machines depending on what domain they are for.

Basically how do I go about this and is it a internal DNS server that I require. Im not looking for someone to give me a complete run down of what to do, but it's a case of not knowing what to look for!

Thanks guys.

Jamie

[Hayl]

no, you definately do not need a dns box for that.

<i think> it can be done with your firewall.

[jme]

I've had a read through the smoothwall site and the docs within the smoothwall install that i have and i cannot seem to find anything that seems of any use. Could it be an add on module?

Thanks Hayl.

[jme]

bump. ;)

[quip]

I may be way off here, but isn't what you're describing just virtual hosting? If it is, configging apache correctly is your solution.

[jumpedintothefire]

but when I get the second server I will need to forward different requests to different machines depending on what domain they are for.

Your going to need to forward a different port number for the second machine. If your 'router' can't do port translation, then your going to have to run apache on a different port on the second box. On the first apache box use a redirect to your external ip but state the port to use, for the domains that live on the second box. You could just have a external dns service that allows you to state the port to use for the connection, that should just connect direct to the second machine on the alternate port.

[knute]

Originally posted by jumpedintothefire
Your going to need to forward a different port number for the second machine. If your 'router' can't do port translation, then your going to have to run apache on a different port on the second box. On the first apache box use a redirect to your external ip but state the port to use, for the domains that live on the second box. You could just have a external dns service that allows you to state the port to use for the connection, that should just connect direct to the second machine on the alternate port.

That's one solution. However, since windows can act as a router, the virtual hosting can control what domain name goes where.

the easiset way would be to simply mount the RootDocument on the second machine to a mount point on the first. Then simply set up your virtual domain to have that mount point be the DocumentRoot.

Unless Virtual Hosting can use the machine name, then you simply set it up that way, and machine one acts as the router.