This stuff is all DNS-related and isn't really related to IIS.
In DNS, you have an A record that points "mydomain.com" to 123.123.123.123.
Then you create a CNAME that points "www.mydomain.com" to "mydomain.com".
In IIS, you just create a new "web" with the above IP address. You can call
it whatever you want, but out of habbit, I call it "mydomain.com".
I don't know how it'd be possible for multiple domains to have the same IP
and yet produce different output to the browser (with the exception of doing
some funky stuff in Cold Fusion--we do this for specific sites that are all
related to eachother for our own company).
Josh
>Danny wrote:
>
>> Oh really. I have one IP address for all the www sites in IIS 4 and it
>> works prefectly.
>>
>> The only problem is really netscape 2 users that cant support httpd 1.1??
>>
>> >But if you don't then how can you get sitename.com to work without the
www in
>> >front of it? It is better to have seperate ip's.
>> >
>> >Danny wrote:
>> >
>> >> U dont understand you don't need a seperate IP address for a new
website
>> >> thingy so why do you bother binding all them additional IP address to
>> the NT.
>> >>
>> >> 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
>> >
>> >
>>
>> 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
>
For more information about this list, including removal,
see this url: http://www.iea-software.com/maillist.html