Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How To Use Host Header Names to Configure Multiple Web Sites with SSL in DNN?How To Use Host Header Names to Configure Multiple Web Sites with SSL in DNN?
Previous
 
Next
New Post
5/24/2009 12:18 AM
 

Stefan Ott wrote

I was able to get a GoDaddy.com WildCard SSL cert to operate on my single install instace of DNN 4.9 with multiple child and parent portals which each have their own host header name (which as far as I can tell is required for GoDaddy.com's WildCard certs) and it all works fine with SSL pages on all portals.  The problem I'm having is when I have any domain name redirect to any of these sites via their host header name and mask the name so it looks like www.sitename.com instead of sitename.myhost.com it won't work with SSL.  I've tried a few different things and just can't figure it out.  Is there functionality for this to work in the beta version of 5?

Thanks,

Stefan Ott

 

A Wildcard SSL cert refers to multiple subdomains for the SAME domain name. This means you can't use it for parent portals because parent portals means different domain names unless you mean Godaddy's UCC cert which can be used with different domain names.

 

If one really needs to use the same ip address for multiple ssl sites then you either use a shared cert where you need an SSL redirector module or you use a different ssl port. The default is 443 so you use 444 and so on. However this is unusual because you then have to put the port number in the url. Plus many firewalls don't have non standard ports open so someone for example at work won't have access.

 

If you use a shared SSL cert, all the portals sharing the cert will display a uri of the site holding the cert which might confuse some visitors. The setup in DNN could be a hassle why it's easy to set up in non DNN sites.

 
New Post
6/1/2009 3:28 PM
 

So I've got multiple domain names.

www.ParentDomain.com (DNN Install)

--->www.subdomain01.com (subdomain01.ParentDomain.com)

--->www.subdomain01.com (subdomain02.ParentDomain.com)

I have a GoDaddy.com WildCard SSL Cert applied to *.ParentDomain.com which covers each of the subdomains perfectly.

The problem I am having is that the subdomains need to have masking applied so they show www.SubDomain01.com instead of subdomain01.ParentDomain.com, which for now is setup with DNS Masking. This makes any SSL page a standard http page because of the problems with the dns name differing from the site name listed in SSL.

What I want to do is use the built in SSL settings on the portal settings page of my DNN instance and have the SSL url set to https://subdomain01.ParentDomain.com, and have it go back to the masked name when not on a secured page. No matter how I try to set it up, I can't get it to work properly. I don't know if there are additional settings in IIS or in my DNS Arecords that I have to modify or what.

If I turn masking on, the site works perfectly without SSL, and if I turn it off the site works great with the hostheader name displayed and with SSL. Am I misunderstanding the purpose of these settings that are native to DNN's SSL settings?

 

Any help is definitely appreciated.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How To Use Host Header Names to Configure Multiple Web Sites with SSL in DNN?How To Use Host Header Names to Configure Multiple Web Sites with SSL in DNN?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out