(1) Make sure that DNS can resolve both sites to the correct IP address (again, either the same address, or two different addresses) (2) Create two websites that point to their respective content (for security reasons, preferably NOT under c:\inetpub -- that's to avoid directory traversal bugs, which you've seen before....like if someone composes a unicode GET request for ..\%systemroot\system32\CMD.EXE, for example) (3a) If you're using two IP addresses, you can configure the website (under the Web Site tab) to listen to a specific address, instead of the default (All Unassigned). [or] (3b) If you have only one IP address (which is typically the case if you're an ISP for example, and you want to point MANY customer sites to ONE single server with one single IP address), you leave the site listening to All Unassigned (although again, for security reasons, I recommend specifying an address), and instead click on Advanced (also on the Web Site tab, just to the right of where you change the IP address). In the top box ("Multiple identities for this website"), assign leave the IP address set to All Unassigned (or specify one, per the comments above, if you like), leave the port set to 80, and enter in a host header that corresponds to the fully qualified name of the site (as specified in DNS) -- for example, www.mysite.com. That's all there is to it! PS -- You'll notice that SSL doesn't support host headers. The only way to host multiple SSL sites on the same server is by changing the IP address or the port. (Typically, you change the IP address, since otherwise clients have to specify the port in their browser, which is pretty ugly). Robert Stewart Douglas Stewart-Douglas Consulting rob at stewart-douglas.com (415) 305-8087 -----Original Message----- From: Chris W. Parker [mailto:cparker at swatgear.com] Sent: Tuesday, July 02, 2002 4:49 PM To: thelist at lists.evolt.org Subject: [thelist] IIS5: two sites on one box, with one ip hi. right now we've got two servers hosting one site each. i need to put one of the websites (the one that is being redesigned) on to the other box permanently. the website that is being redesigned is configured so that once a request for the site comes to the server, the server redirects that request to the other website. basically both domains are pointing to the same place as far as the user is concerned. however in actuality one box redirects to the other. it was suggested to me by customer service at earthlink that i change the A record of the site that is down to the same IP address as the site that is up. effectively making it true that both domains are both pointing to the same ip address. this sounds correct and fine. the problem i have though is that i don't know how to setup IIS so that when the time comes to bring the new site up, the ONE ip address can point to two seperate websites on the same box. he said that the server will know which one is being requested based on the headers of the request. again, that's fine and dandy, except that i don't know how to configure iis to understand this. can someone please instruct me or lead me to a document that gives step-by-step instructions on how to do this? everything i've found regarding this assumes too much. thanks a lot. chris. -- For unsubscribe and other options, including the Tip Harvester and archive of thelist go to: http://lists.evolt.org Workers of the Web, evolt !