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 ...Double SubDomain Portal AliasDouble SubDomain Portal Alias
Previous
 
Next
New Post
2/19/2009 1:00 AM
 

I have a requirement to have a dynamic double subdomain point to a DNN portal using a single subdomain wildcard portal alias.  The subdomains are dynamic vapour. That is, I want the web user to be able to access my portal using one of the following URLs without actually having to create an alias for the base subdomain name:-

mystore1.domainname.com or www.mystore1.domainname.com
or
anotherstore.domainname.com or www.anotherstore.domainname.com

Now I have the mystore1.domainname.com and anotherstore.domainname.com working just fine by configuring a single portal alias: domainname.com.  DNN interprets this as all subdmains of domainname.com point to this portal.  Because my DNS A-record directs all subdomain wildcards for this domain to the fixed IP, and IIS passes all headers to the DNN portal, it works perfectly. All great - a single SSL certificate is all that is required since the site runs in the same domain for all subdomains due to URL rewriting.  That is, once you connect to the site using mystore1.domainname.com, this URL becomes simply domainname.com, as does anotherstore.domainname.com becoming just domainname.com (the alias name) which is wonderful.

Then one of my store owners forgot to leave out the www prefix and told all his customers is URL was www.mystore1.domainname.com.  ARRRHH.  The URL doesn't resolve because it appears as if DNN only does subdomain wildcards one level deep. If I add a second portal alias entry as mystore1.domainname.com, it works, but then the SSL certificate is invalid as this is a different subdomain.  The only solution without proper portal alias wildcard support is to purchase a wildcard SSL certificate which will cost a small fortune.

So the BIG question is, does anyone of there ever managed to get DNN portal alias to work so that a single alias on the base domain name will work, not matter how many subdomain prefixes are used. That is, all of the following URLs should resolve to the the same portal using the portal alias domainname.com:-


domainname.com
mystore1.domainname.com
www.mystore1.domainname.com
anotherstore.domainname.com
www.anotherstore,domainname.com
 

 
New Post
2/19/2009 1:28 AM
 

Chris

Without digging into the DNN Core code, my suggestion would be to write a very simple Http Module that was above the UrlRewrite module in your httpModules list.  This module would just check the domain name for incoming requests, and if it found you had a two-level deep subdomain, it would do a 301 redirect to the correct subdomain.  The module would just ignore anything else.

Of course this assumes you've got either the skills or someone with the skills to write this for you - but I think you're going to have to come up with a custom solution for the problem.  The code to identify which portal alias is running is shared between the Core HttpModule and the Core library, so you'd have to start modifying them to fix the problem - you probably don't want to do that.

-Bruce

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Double SubDomain Portal AliasDouble SubDomain Portal Alias


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