I know there is lots of info here about portal aliases, etc. But I just want to ensure that I am getting it right for my particular situation.
I am basing my new (first) store on the DotNetNuke platform using ASPDotNetStorefront's ML/DNN version.
As we all know (hopefully by now), in DNN it basically lets me set up multiple portal aliases in the database such as
So when a request is sent to the DNN install it looks in the db to determine which site to send it to. In this case the first two go to the same site for the same domain homeschoolportals.com.
The third option is for either a temporary access until a domain is pointed to the site or for what is called a child portal. That way sites can be built in advance of transferring the domain to the new nameservers. Or if a domain is never acquired, the site just exists as a child (clipped) off the parent domain (homeschoolportals.com).
In my control panel (DotNetPanel) I add the domain uncommongames.com and then assign that to a website with a root directory. So now IIS knows what directory to send the http traffic to. DNN handles it from there.
So finally here is my question. I want users to access my site using www.uncommongames.com . But I also want it accessible by just uncommongames.com. If I don't put in the portal alias in the DNN db. It will not show up as a page.
So can I take the plan uncommongames.com out of the DNN portal alias table and do some kind of redirect directly in IIS so that both www.uncommongames.com and uncommongames.com both show up at the same site, but don't get indexed separately to cause SEO issues. Hopefully some of the DNN / SEO experts out there can chime in on the best solution.
Thanks for any information you can provide.