Boy oh boy, I can see why people might get this wrong.
Thanks for your input Bruce, but your explanation has confused me somewhat.
So I have drawn a diagram, Multi site for dummys..... includes me apparently.
When you say "On the Clients pc's"
I dont get it, I thought you only had to set the host file on the server
As per my diagram
request for test.3d.com.au comes out of das cloud - down the interWebs
DNS points it to 120.146.159.14
ADSL takes this and port forwards the port 80 request to internal pc on 192.168.0.105 - known lovingly as "Mr Server"
www.3d.com.au has been here for quite a while, now served up as a static page by HOST.exe
All is good
NOW, we add example (59)'s Site1.DLL as a player, set to respond to test.3d.com.au as a sub domain.
The servers host file takes the name "test.3d.com.au" and points it to 192.168.0.105
And when you open firefox on the server, it works
Now someone in another city (say London) opens firefox and asks for "test.3d.com.au"
The domain 3d.com.au resolves to 120.146.159.14:80
That hits the adsl modem, and gets forwarded to 192.168.0.105:80
The host file takes the sub domain and directs it to 192.168.0.105:80
The host picks this up and from the value Q sees that it was destined for the sub domain "test" and looks in its TPS file to find the DLL it needs to hit.
SO = = = = = Is this correct Bruce? and if so, what do you refer to as the clients pc's, are you saying the pc in London is the client to the server?
Thanks
Kevin
[attachment deleted by admin]