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

At my last company we had a development server where the developers could create websites/tools, upload to the development server and when setting up the host header in IIS would use * Eg

In theory allowing us to add add as many websites as we wanted (by using a different name for *)..

All staff within the company could then access this URL's and use the tools (in house only, not externally e.g

I'm wondering how I can do something similar at my current company -

I've asked IT for:

  • windows server 2008
  • iis7
  • sql server
  • .net 4.0

Regarding the naming of multiple sites what else would IT need to configure so that I can do something similar...

or is there another way of doing this. basically what i want to do is:

  • create websites is .net
  • upload to server available to internal staff only
  • give an easy way for staff to access it (with a easy to remember url)
share|improve this question

migrated from Jul 18 '11 at 12:07

This question came from our site for professional and enthusiast programmers.

up vote 1 down vote accepted
  • create websites is .net

Sounds like you've got this covered with the Microsoft stack you've chosen. Not to complicate things, but you might want to look at setting up the Hyper-V role and running the server as a VM down the road to give you snapshotting and portability.

  • upload to server available to internal staff only

This could be SMB (file shares accessible to only the development team), or WebDAV, or plain FTP, although if this is for LAN access only, I really don't see the value in FTP. IIS can be accessed remotely through inetmgr (IIS Manager), as well as SQL with SQL Management Studio Express.

  • give an easy way for staff to access it (with a easy to remember url)

IT needs to setup a wildcard DNS entry in the DNS Server to resolve * to the IP of your new dev server. They should know how to do this. This will allow you to create as a host header entry in your corresponding IIS sites.

share|improve this answer
one requirement i forgot to mention was that i want users to be able to authenticate using active directory... is there a particular requirement needed for the server. If this server is on the network is that enough? – raklos Jul 18 '11 at 14:48
the server needs to be a member server on the existing Active Directory domain. As far as Web-based Active Directory authentication, that's another question altogether. – gravyface Jul 18 '11 at 14:52

IIS supports multiple web sites on a single server via three different methods, assigning each site a unique IP address, assigning each site a different TCP port number or the preferred way is using the host header name

Take a look here:

share|improve this answer

I would suggest putting a DNS On top of it and redirecting internally a zone to it, so that new subdomains dont ahve to go through IT.

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.