Jump to content

Recommended Posts

Posted

We're running IIS7 and already have a few sites running on port 80. These are all internal sites so it's working using URLs such as http://servername/site1, http://servername/site2 etc which isn't an issue. Going forward, we need to run another site off of this server however it needs to be eventually accessible externally.

 

Am I right in thinking that this could be achieved by creating the site in IIS and then using host headers so that it can continue to operate on port 80, rather than giving it some other random port? If I was to set the host header as lets say site.mydomain.com then create the records on the domains DNS server to point site.mydomain.com to the IP of the IIS7 server, then this will all work nicely? That would do away with needing to use lets say site.mydomain.com:1234.

Posted

yes absolutely, this is how its done all over the world.

 

Host headers make things really easy, you can run hundreds of sites websites from the same server.

 

It takes about 5 clicks to set one up. Just register a domain, (or sub domain) and type it into the host header box on a new website in IIS. Its that simple.

Posted
yes absolutely, this is how its done all over the world.

 

Host headers make things really easy, you can run hundreds of sites websites from the same server.

 

It takes about 5 clicks to set one up. Just register a domain, (or sub domain) and type it into the host header box on a new website in IIS. Its that simple.

Great, thanks.

 

It almost sounded too easy for Microsoft so I questioned it.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...