> So using CNAME's would take the place of relying on host headers? In DNS, CNAME records allow you to map multiple hostnames to a single IP address. More specifically, you create an A record mapping a hostname to an IP address, then you create CNAME records mapping hostnames to the hostname you specified in the A record. The end result is, people can enter any of those hostnames in their browser and get sent to the same IP address. If you want to have multiple IIS web servers, each with its own certificate, corresponding to multiple hostnames, you'd simply give each one its own IP address, and its own hostname in your DNS. If you want to have a single IIS web server, with a single certificate, corresponding to multiple hostnames, you'd use CNAME and A records as mentioned above with the proviso that the certificates could not be used for trust purposes as we discussed previously.
> And, if so, since I wouldn't be using host headers I could > put multiple SSL sites, each with their own IP on the same server? Yes. > And, SSL traffic would be light, at least at first (hope this > is an app and service I can sell...) so I shouldn't need any > SSL hardware acceleration. Probably not, no. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:249203 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
