This is one way it could be done. It may depend where your internal website is hosted. So first of all, I am assuming your clients connect to the WinGate server via proxy. So what we want to do is catch a DNS request on the WinGate server for e.g.
www.wingate.com, and reply with its address as a computer on the local network. To catch a DNS request before querying a DNS server, we use the "hosts" file.
On a 2k / XP machine the hosts file is located at C:\WINDOWS\system32\drivers\etc . Open the hosts file with notepad. You will see a "localhost" address in there. We will add the new
www.wingate.com below it.
e.g
127.0.0.1 localhost
192.168.1.1
www.wingate.com
Then save. Please make sure there is no file extension placed on the hosts file. You can quickly test by opening a command window and pinging
www.wingate.com
(Windows) Start menu --> Run --> cmd --> ping
www.wingate.com
Now whenever a proxy request comes in for
www.wingate.com, the host file will be checked, and reply with the IP Address without requiring to Query a DNS server on the internet
*** If you require to do this without using the proxy, then you will need to modify the hosts file on each client computer. This can be done with a policy or login.bat file. If I hear of a better way, will advise.