> 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.
So, I'd create an A record for each separate domain name, then create a CNAME record pointing to the corresponding A record? That sounds like using CNAME's and A records as I would Host Headers. Is that a correct understanding??? (I doubt I'm getting this right) GoDaddy's instructions at the top of the dialog where I enter an A record, states, "Do not enter www.domainnamegoeshere.com" as the host name for an A record." However, it seems I might be able to enter "domainnamegoeshere.com" in the A record, because it's addressing the fact the "www" should not be entered in the A record with the domain name. So, in the GoDaddy DNS manager, when it says WhiteStoneMedia.com is the domain, I can still put other domains in the A records, such as Site1.com and use CNA ME's to route domain requests to www.Site1.com? Doesn't seem logical. How, at the point the request for a domain name gets to my server, would the server know how to route traffic without Host Headers or something else on the server to direct traffic? Rick -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 08, 2006 12:21 PM To: CF-Talk Subject: RE: SSL Certificates > 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:249214 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
