Maybe I've been doing this wrong so far, but it's been working in the past... Simply, I'm trying to setup multiple domains to resolve to a primary domain. However, when the page loads I want it loaded under the primary domain due to module licenses, map keys, etc. Up until recently, I'd simply added the domain alias in our WebPanel control system. Even without the domain aliases defined under the Admin / Admin Settings / Advanced / Portals section, the site would still load, and when the user entered DomainAliasA.com it would resolve in the address bar to PrimaryDomain.com. Everything was happy in developer-land (at least as far as I could tell).
However, I recently upgraded a site from 4.9.5 to 5.6 and it seems that now when I visit the site using the aliases, they get added automatically to the domain alias list*. The problem is that, now when a user visits DomainAliasA.com, it doesn't resolve to PrimaryDomain.com and is causing problems with modules which were registered on a per-domain basis and Google Map API Keys are throwing a fit too.
Simply: has the behavior of how DNN 'handles' / 'intercepts' portal aliases changed? Is there a better method I can use to help me avoid these licensing problems, and an even larger problem - the appearance of duplicated content to the SEs?
*Method used to test this:
- Log into site using PrimaryDomain.com
- Check Admin Settings > Portal Aliases
- Only domain listed is PrimaryDomain.com
- Log out
- Open new browser (to avoid any cookies / stored info)
- Visit DomainAliasA.com
- Don't login, simply let page load and close browser
- Open new browser, visit under PrimaryDomain.com
- Login
- Under Admin Settings > Portal Aliases, find DomainAliasA.com was added automatically