Hi. Just upgraded from 5.6.0 to 5.6.1 and trying to get a handle on the new Portal Alias feature. The functionality is stated as follows: You will now be able to designate a single portal alias as the default alias.  The administrator can specify special handling for the portal aliases including the ability to use the default portal alias as the base domain for the “canonical url”.  Alternatively, the administrator can choose to use a 301 redirect so that all portal aliases will be redirected to the default portal alias. I h

I have 3 portal aliases set up - mysite.com, www.mysite.com and localhost/mysite. I see the new option group - none, canonical, redirect. But how do I designate 1 portal alias as the default? I'd like to establish www.mysite.com as the default and select the canonical option.

Thanks.

---

Vinny Malanga
IMI Software, Inc.

I have a similar problem, and it follows the issue I've been having since 5.6.0... Domains (not actual, naturally): www.Domain1.com www.Domain2.com www.Domain3.com So, when the modules and scripts used were setup (and registered), they use Domain1.com. This is great if that's the domain the site visitor uses. However, if they come in on Domain2 or Domain3, those domains are still displayed / resolved in the title bar, and is causing many issues with things like Module Registration, Google Maps API Keys, etc.

Previously, if I had the default domain and nothing else setup in DNN, when I visited Domain2.com it would resolve properly to the primary. However, if I had setup the domain alias in the portals table, it would resolve to the domain used by the visitor. So I simply didn't use the domain aliases in the portal tab (it let IIS handle it I believe). This created all kinds of havoc with 5.6.0 since it would auto-add the aliases as they were visited.

So 5.6.1 is released and I squeal with joy when I see the "301 Redirect" option mentioned. My experience with these has been that when setup they would resolve Domain2.com to Domain1.com in the title bar and everyone was happy. So in DNN if I set them up WITHOUT the alias domains in the table, it would resolve automatically, however if the alias domains WERE listed in the portals table it would resolve to those alias domains, I simply just would always list the primary and let IIS handle the rest. I have recently upgraded a test domain to 5.6.1 and conducted several tests. However, no matter if I choose "Canonical" or "Redirect" it still resolves to the alias domain, and is still causing issues with scripts and modules.

Is there a particular setting / setup I need to check for in IIS in order to get this to work? ( I have sites running on servers with IIS6 and IIS7)
Is this how it's supposed to function?
Help?

Edits: Editor mangled my post, had to add back some sentences it decided were not happy I think I may have inadvertantly made it think I was trying to  "little bobby drop tables" the thing. (Reference)

---

Wells Doty Jr
Online Content Development

What would the best practice be for having setup three portals as seperate sites?  I have three clearly different urls setup as parent portals from the main url.  I wanted to take advantage of DNN's ability 5.6.1 with portals not having to host a new site, but want to build and drive traffic up for these seperate entities.