On Friday, December 31 at 04:20 PM, quoth Andreas Aardal Hanssen: > On Thu, 23 Dec 2004, Kyle Wheeler wrote: > >> The easier solution is to use only one domain, but have it resolve to > >> several A records. This gives you the same flexibility with regards to > >> scaling. > >We have run into similar problems with our own server. What it has > >boiled down to is: each domain that *really* wants it's own SSL > >certificates gets it's own IP address, and the rest share an address and > >key. From the user's perspective, there's usually very little > >difference. > > You can simply register several A records on the same domain; that solves > the problem.
Right, but the domain name is stored in the SSL certificate. Thus, when I try and contact imap.domain1.com, and the SSL certificate it is using says it's for imap.domain2.com, my email client complains bitterly: as it should. How does multiple A records solve the problem? Can an SSL certificate list multiple domains it is valid for, maybe? ~Kyle -- Art, I suppose, is only for beginners, who have made up in their minds to be content with symbols rather than with what they signify, with the elegantly composed recipe in lieu of actual dinner. -- Aldous Huxley
signature.asc
Description: Digital signature
