I have some windows user logging into a MS terminal server to do some testing. The user would enter the url test.net. Instead of going to our live site, I would like it to point to our test IIS web server.

Modifying the host file doesn't work for some reason for http (request for https work), it would go to our live site. We need it to resolve both https & http pages on the site. Our gateway needs to be on due to the many subnets we have (other factors too).

Would adding a seperate bind server work? For example, on my terminal server where the user logs in, I would reference the new dns (bind) server. Then from the new dns server, I would point test.net to my test IIS server?

Would this work?

Thanks in advance,
john

if it's just for one URL, i'd probably just add it to the hosts file on each client to achieve this. If you have lots of clients then that's more work then a name server might be better solution, but not sure why you'd need a brand new one... can't you just add it to what you already use?

acid,

For some reason, the host file resolves only the "http" url, but it misses the secure "https" url (it goes to our live site).

We have only one client.

Any idea?

john

That's not possible. DNS and HTTP(S) have nothing at all in common. Maybe your browser is doing something funky with proxies?

I am scratching my head. The application has embedded links, images which is customized as part of the whole application by the vendor.

If I altered the host file, some page/links wouldn't load correctly.

john