I've just started using multiple websites/IP addresses in IIS for a DNN instance where SSL is required for several different domains (incl aliases).

There seems to be some sort of caching/updating issue happening, where changing module settings from one site isn't taking immediate affect when loading via another IP address.

Recycling the application pool is sorting this immediately but is there something else that can be done?  Possibly a specific setting that will sort this?

Thanks

Hi Jeff

Thanks for the reponse.

From looking at all the information I could find, here and elsewhere... setting up the separate IP address was the only clear way to run multiple SSL certificates for domains.  Is there another way this can be done?

I have several domains that are all tied in, same users as well as data, profiles etc but requiring separate portals, shown in different ways (eg child folders) and using SSL.

Is DNN not capable of this setup?

Hi Sebastian

I have quite a few more than 2 IP addresses... and it may be a solution to look at other SSL certificates but the price of a multi-domain certificate is considerably higher than single domain SSL certificates, especially as I only need a couple of the most simple certificates at the moment and without all the trimmings on offer.

Thanks, and will see what can be done but from speaking with certificate providers I may be in for a consideable increase in cost.