Hello:

In a recent update to DNN, someone added a 'feature' to redirect all requests to a portal to the root 'alias' for lack of a better term. The question is, I need to access the same portal from multiple URLs, most notably when I access a portal from a development URL and a live URL. On my dev machine, the URL is http://localhost/dotnetnuke4. When I access this from a network location, http://artemis/dotnetnuke4, the new default behavior of DNN is to redirect to the lowest numbered alias, in this case the first, which of course does not exist on the other machine.

The question is, how can I restore the behavior where I can access my portal from ANY of the aliases configured for it without the annoying redirect to a non-existent URL???

THANKS!!!!

Hello John:

Thanks for taking the time to answer my question. I don't think I was clear enough by what I meant: I have the two aliases, localhost/dotnetnuke4 -AND- artemis/dotnetnuke4 pointing to the same portal id 0. Additionally, say I am working locally on a site that I pulled down from my web server, I might have a third alias defined for the same portal. Before, I was able to access Portal ID 0 from any of the defined Urls without being redirected to the lowest ID (of the ALIASES, not the Portal ID).

Again, all three aliases are pointing at the same portal, I just want to be able to continue to access that portal with the alias I called it with, because of either name resolution or product limitation issues imposed by Micro$oft not enabling multiple web sites on Windows XP Pro.

I hope that was clearer, I usually think better after a good workout!

Thanks Again!