Hi Jeff,

That's really interesting. 

Can you clarify one thing for me?  How can a search engine have any knowledge of how many hits I get?

I can see that it knows how often my site is presented in its search results; I can see that it knows how much traffic that particular engine sends to my site. 

How can it know about actual hits?  Maybe they come from bookmarks, from the links in my email newsletter, from links from other sites.  I don't get it.

It is not about hits and traffic but page ranking. I suggest to simply google about duplicate content.
 

IMHO this is a decent technical answer but a poor usability and SEO answer.

I think that the dnn core should allow for designating one of the aliases as the primary aliases, and also an option for having a non-primary alias 301 redirect. The reason is two-fold:

1. Access. Most people don't have access to IIS that it is running on to put in such a redirect, and some don't have the ability/access to put in a DNS forward with their hosting provider either. You guys need to code in this reality.

2. SEO. If a person has multiple aliases, they should all 301 redirect to the primary alias.

Because dnn is intercepting all the requests anyway, in truth I don't see a real technical reason why dnn code cannot do such 301 redirects. This just reminds me of other things that dnn does that are a few years behind on SEO optimization.