HI, when we first installed and setup our DNN Pro site we were advised to create our portals as new sites in IE7, each portal running in their own App pool.
This we have done and have currently 2 portals using a different domain name, we will eventually have up to 20 portals using a number of domain names.
When we inquired about securing the various sites logins using https certificates it came to light that this approach is wrong and we Recieved this advice
DNN should run DNN under a single IIS web site entry.
If we run multiple web site entries for each portal in DNN, DNN will determine this as multiple web servers in Host > Manage Web Servers. This is then determined to be a web farm configuration, which will turn on the Shared Caching Providers. Since we are not using a web farm configuration, multiple errors will occur due to the web request caching provider and Host > Schedule will not run. Meaning that the Search Crawler has not spidered our websites.
It is recommended to run DNN under a single application pool and IIS web site entry. After this is done, deleting all entries in the WebServers table will allow the scheduler to run normally again.
This recommended configuration of DNN will only allow for a single SSL certificate to be installed in the IIS web site entry. This is a limitation in IIS 7.

Obviously we cannot afford to buy 20 licences for each domain.
Apparently IIS 8 allows multiple SSL certificates to be bound to host headers, does anyone have any knowledge of II8 and can confirm this?.

Other than build a new hardened web server with II8 (if true) and all the problems of moving licences and sites domains etc, are there any real issues with our current setup and is there any workarounds we can use to get around applying https to secure each site.

Hi Chris, yes IIS7 .

I really hate to say so as most advice has been brilliant but it was DNN Pro support.
We set up our portals and webserver according to that initial advice and now find ourselves with a problem.
One of the reasons we choose DNN was the multi portal option and the ability to share data accross portals easily.

We never thought much about multiple domain names being a problem and it was never raised during our sales webinars, but are now wondering what the best approach is.

 Chris, are you saying our current set up is ok with multiple sites and app pools and the domain names as host headers.
Or should we make each portal a virtual directories running under one app pool? and if yes could  we still use different domain names in host headers.
DNN Corp were suggesting multiple instances for each domain but that is unrealistic and unaffordable to have multiple licences

Any advice as to a workaround would be welcome.