I didn't know this could be done for multiple content areas being served
from the same IP and port. It turns out that it is something that's
dependent on the client though, so it doesn't work quite as well as having
each domain on a separate IP (if the content to be served is different). I
guess if you're limited on IPs, it's a handy approach though.
Host Header Name:
For your server to have a domain name, you must register it in the Domain
Name System (DNS). A domain name server then maps your registered domain
name to your IP address, enabling requests addressed to your domain name to
reach you. You can assign multiple domain names, or host header names, to a
single IP address. If the client browser supports the use of host header
names, the name the user types is passed in the HTTP header as host. The
server then routes the client to the correct Web site. If the browser does
not support the use of host header names, the server responds with the
default Web site if a default Web site is enabled. Otherwise, the client
receives an error message. If the Web site requested in the host header is
stopped, the client receives the default Web site. Therefore, it is
recommended that an ISP use the default Web site as the ISP home page,
rather than for a customer site.
Josh
>n>This stuff is all DNS-related and isn't really related to IIS.
>n>In DNS, you have an A record that points "mydomain.com" to
>n>123.123.123.123. Then you create a CNAME that points
>n>"www.mydomain.com" to "mydomain.com". In IIS, you just create a new
>n>"web" with the above IP address. You can call it whatever you want,
>n>but out of habbit, I call it "mydomain.com".
>
>n>I don't know how it'd be possible for multiple domains to have the
>n>same IP and yet produce different output to the browser (with the
>n>exception of doing some funky stuff in Cold Fusion--we do this for
>n>specific sites that are all related to eachother for our own company).
>
>n>Josh
>
>n>>Danny wrote:
>n>>
>n>>> Oh really. I have one IP address for all the www sites in IIS 4 and
>n>>> it works prefectly.
>
>n>>> The only problem is really netscape 2 users that cant support httpd
>n>>>1.1??
>
>n>>> >But if you don't then how can you get sitename.com to work without
>n>the www in
>n>>> >front of it? It is better to have seperate ip's.
>
>n>>> >Danny wrote:
>
>n>>> >> U dont understand you don't need a seperate IP address for a new
>n>website
>n>>> >> thingy so why do you bother binding all them additional IP
>n>>> address to the NT.
>n>>> >>
>n>>> >> For more information about this list, including removal,
>n>>> >> see this url: http://www.iea-software.com/maillist.html
>
>
>n>>> >For more information about this list, including removal,
>n>>> >see this url: http://www.iea-software.com/maillist.html
>
>
>
>n>>> For more information about this list, including removal,
>n>>> see this url: http://www.iea-software.com/maillist.html
>n>>
>n>>
>n>>For more information about this list, including removal,
>n>>see this url: http://www.iea-software.com/maillist.html
>n>>
>
>
>n>For more information about this list, including removal,
>n>see this url: http://www.iea-software.com/maillist.html
>
>n>
>
>CMPQwk 1.42-21 9999
>
>
>For more information about this list, including removal,
>see this url: http://www.iea-software.com/maillist.html
For more information about this list, including removal,
see this url: http://www.iea-software.com/maillist.html