Topic: Virtual Domain Name

[Lindsay Teychenne]

I installed e-smith 4.1.2 a few days ago The primary domain is (eg) "maindomain.com" and most things work as expected .

Except for 1 thing. I have an ISDN line and a cisco 775 router and been running a number of different web servers happily. I have put those servers onto the local network all using e-smith as the router. I want to serve one of the machines up to the web and have a dns entry (at my isp) for it (among others) pointing to the e-smith server.

I expected (based on advice I got) that e-smith would read the intended domain name and direct the traffic to the machine I had setup in  hostnames and addresses. I have tried both the full domain name (fmp.maindomain.com) and just the machine name "fmp".

It all works fine and tests fine with both setups from within my local network but noone from outside my network can access it directly. They only get the Primary Domain ibay when they try to access fmp.maindomain.com.

This is a fairly crucial feature for me. e-smith exactly serves all my other needs and I really don't want to revert to my previous setup.

Is it something I am not doing properly or are my expectations wrong?

TIA
LIndsay

[Des Dougan]

Lindsay,

From your post, I think you're looking for the Apache Proxypass feature. There is a thread I think will help you on the devinfo list (which you can search).

Des Dougan

[Charlie Brady]

Lindsay Teychenne wrote:

> I expected (based on advice I got) that e-smith would read
> the intended domain name and direct the traffic to the
> machine I had setup in  hostnames and addresses. I have tried
> both the full domain name (fmp.maindomain.com) and just the
> machine name "fmp".

"hostnames and addresses" has no effect on external access to the server, it only affects the internal resolution of names. You need to set up virtual domains using the appropriate manager page.

Charlie