Date:  10/29/2009 05:27:50 PM Msg ID:  004048
From:  FoxWeb Support Thread:  004047
Subject:  Re: Question about Virtual Servers section
First I want to make sure that I understand what you mean by "internally". Are you saying that when you are connected to the server via Remote Desktop, you can't resolve hq.customerdomain.com from a local browser? If yes, you could add this domain to the hosts file in C:\Windows\System32\drivers\etc. Alternatively, you could use "localhost" as your server name. FoxWeb does not require that you add localhost in the Virtual Servers page, so you don't need an additional license for it.
 
FoxWeb Support Team
support@foxweb.com email
Sent by Ali Koumaiha on 10/29/2009 11:23:00 AM:
I recently purchased a copy of FoxWeb and i just installed it for a client.

everything is working great on win2k3.. 1 Server License for them.  works perfect so far.

i created a sub-domain (they hosted with Godaddy), hq.customerdomain.com and made it point to the foxweb internally (opened port 80).

in foxweb control center, under virtual servers:
Server name: hq.customerdomain.com
IP-address: the IP address
Program Root: [default]


They use Comcast high speed internet, and i can access the domain from anywhere outside, with the ip and the server name, no problem.

when, internally, on the same network.. they cannot resolve it. 

if i change the server name to [TheServerName], it works as in IntraNet, but, external, they can't use it obviously.

What the best solution?

Purchase additional server? or something with the routing?