This is possible. I suggest that you have these two websites: Default website New sample website Leave the "Default website" with the default port (80) and the IP Address information to "All unassigned". For the "New sample website" use the default port (80) and under IP...

Hi One way of solving this could be using hostheaders on your website. Although you might have to add a record to your internal DNS og hosts file for this to work proberly. For your new website, hosting you current sample page on port 1080, you can change the port back to port 80 and then add a hostheader...

Hello. This will probably be a long and very complex question, so sit back and enjoy the ride (and feel free en point out any flaws in my logic/flow). I have the ungrateful task of making new websites for our customers (we make travel websites, and as such have a lot of domains, accounts and other stuff...

I currently have about 50 sites/domains hosted from IIS on my server and they all use host headers. I only have 1 ip on my server. Is there any performance advantage to setting up a unique ip per site/domain, or at least the more high volume ones?