Windows Thread, IIS - Understanding correctly? in Technical; We're running IIS7 and already have a few sites running on port 80. These are all internal sites so it's ...
11th October 2012, 09:59 PM #1
IIS - Understanding correctly?
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.
12th October 2012, 09:52 AM #2
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.
12th October 2012, 09:57 AM #3
(for reference) Name virtual host in apache .
12th October 2012, 12:25 PM #4
Originally Posted by zag
It almost sounded too easy for Microsoft so I questioned it.
By OverWorked in forum Windows
Last Post: 31st March 2006, 01:34 PM
Last Post: 7th March 2006, 04:12 PM
By fooby in forum Web Development
Last Post: 13th February 2006, 04:30 PM
By tosca925 in forum Windows
Last Post: 6th February 2006, 12:52 AM
By kingswood in forum *nix
Last Post: 8th September 2005, 10:51 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)