Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a server with three sites on it (the default site and two applications). I want to set up some test sites (classic ASP) on the server but if I put them under Default Web Site I can't set them as the root for their own applications.

In other words, my application uses non-relative paths and I want to be able to test the thing without redoing how I do my includes all over the app.

What are my options? I thought about setting up Host Headers but I don't have access to any name resolution for the server- that's handled by someone else.

share|improve this question

If you want to setup TEST sites then you can use Host Headers and just modify the hosts file on the local machine(s) connecting to the test site. I do this all the time. If you want many people to "test" these sites, then that won't work but if it's just you and a couple of others, this should work nicely.

share|improve this answer
In my case, I VPN into the domain (let's call it Sample.Com) and to the web server (Server.Sample.Com), which is accessible both inside the network (the Sample.Com domain) and outside (the Internet). I was under the impression to use Host Headers, I'd need to make DNS changes on the DNS server for Sample.Com to coordinate with the Host Headers. For example, if I wanted Test1.Server.Sample.Com to be a root app, I'd need to set the DNS server at Sample.Com to forward Test1.Server.Sample.Com to Server.Sample.Com. Or am I making this too hard? – Caveatrob Oct 25 '11 at 3:39
For testing from your own machine, you don't need dns changes. modify the HOSTS file on your local workstation and create entries for each hostname (which corresponds to the web site in IIS running with your custom host header entries) and the IP address that host should resolve to. Your browser will use the hostname to populate the "Host: " http header and IIS will route to the correct web site instance. – mahnsc Oct 25 '11 at 12:30
Okay but to set up testing for my client on the internet I do need to make dns changes. – Caveatrob Oct 25 '11 at 19:44
Is there any way to set up an IIS-root-level rewriting thing to make the urls work? – Caveatrob Oct 25 '11 at 19:44
Sorry if I wasn't clear enough - if YOU - as in you are the only person who needs to access this - want to have a test/dev site, then you can do this with a Hosts file and not worry about DNS. If there are 3 or 4 or 5 of you (ie, a small number) you can instruct the others to do it too. If you want to create a dev/test site that will be used by dozens, hundreds, or as a "public beta" than this is NOT a practical solution. – Multiverse IT Oct 25 '11 at 20:02

Any newly created website needs at least one or more unique values for any of the following binding options:

  • Protocol (http, https)
  • IP Address
  • Port number
  • Hostname

The easiest for your situation is possibly to use a different port number.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.