You can do this by creating additional IIS sites and pointing them to your DNN directory. For example, if you have all of your DNN files in the "DNNfiles" folder and two web sites, 123.com and 789.com, both entered as host headers in an IIS site called "DNN" which points to "DNNfiles"; you can create another IIS site called 123, make sure it handles the 123.com host header and points to "DNNfiles", and that site can have its own SSL certificate. Hope that makes sense.

Tim

I had exactly the same question and am very glad to have found your posting on this, Tim. It worked like a charm. Thank you!

I found on my first attempt I had neglected to enter the 123.com host header in BOTH IIS website instances -- the original DNN site and the new 123 site. The mistake wasn't apparent until I applied my "123.com" SSL certificate to the 123 site, and things didn't work correctly.

The second thing I discovered was that it's important that the 123 site run the same version of ASP.NET as the original DNN site. In my case, that was ASP.NET 2, which is not the default. I discovered this on getting an error message on trying to bring up the web site, causing me to dive into the server event log to see why.

Hope these tips save someone a couple of little detours!

Steve

I'm running IIS 6 on my own Win2003 server. My problem is in setting up the additional web site in IIS. I must be missing something.

The DNN web site directory is "files." Previouly, I had set up a second web site in IIS, "dnn2," so that I could give the corresponding DNN portal, "dnn2.com," its own SSL certificate. It works perfectly.

The problem comes in when I try to add another web site in IIS. I point it to the same DNN directory, "files," and give it the usual tcp port 80 and SSL port 443. When I try to start it in IIS, I get:

"IIS was unable to start the site. Another site may already be using the port you configured for this site. Please select a unused port for this site."

I can get it to start if I change the SSL port to some other value than 443 -- but I need it to be 443 for the usual reasons.

Help! What am I missing?

Steve