>>>>Is this possible?
>>>
>>>Yes, you can do this with only 1 IP address. We are actually doing this ourselves, instead of assigning an IP address to each site, specially low (i.e. VERY low) bandwidth sites.
>>>
>>>To do this, in your DNS, simply create the A record to point to the IP address you want to use (always the same one for each site). The special thing that must be done is in IIS itself. You create the web, as you normally would, and specify the IP address as usual (the one you want to use). Before starting this site in IIS thought, right-click on it, select properties and click on the "Advanced" button to the right of the IP address of the site. In this window, Type the full DNS name of the site (i.e. www.thisismyweb.com) in the "Host Header Name" field. OK your way out of the property page and start the site.
>>>
>>>If you test this in your browser afterwards (make sure the DNS server entries are refreshed and updated), you should be able to see the site (if there's content) or the fancy and classy, always beloved 404 error. The only thing is, if people try to access the site through it's IP address, they will get the site that does not have a host header name entry (the default site for the IP).
>>>
>>>This is also a useful thing to do for normal sites, since leasing/renting/buying a subnet (no matter how small) can be quite expensive. This way, you can run an entire hosting site under 1 IP address, mail included!
>>>
>>>Hugo Dahl
>>
>>Thanks Hugo,
>>
>>I had a hunch that this might be the solution. I have so far managed to avoid using HostHeaders, but i'll have to delve in now. Don't I remember something about HostHeader usage only working with newer browsers?, Or is it OK with all browsers?
>
>As far as I've axperienced, it works with all browsers since it's the server that does the translation. The only problem I can think about is if an older browser resolved the IP address, then tried to access the site through the IP address (not sure if they do though). I wouldn't think so since this is how Unix based web servers have been doing things from day one.
>
>But, if you find out for sure, please let me know.
>
>Hugo

Hi Hugo.

A browser must be HTTP 1.1 compliant in order to use Host Header Name, cause the IIS looks for information sent by the browser. With IE 3.x and Nav 3.x (and later) the HTTP header contains the actual domain name requested. IIS uses this to determine which site should answer the request.

If you use a non HTTP 1.1 compliant browser you have to program a core page to display all available sites on an IP to allow the user to choose which site to use.

If you use SSL Host Header Name is not supported either.