I've set up a few DNN sites for clients. It's all gone pretty smooth. However, when they've both gone live whenever the live URL is accessed it redirects back to the first portal alias that was configured during set-up and testing.

I've even gone into the database and changed the first created portal alias to the live site URL, but it still does not work and always redirects to the first one. This has happened on two sites now and I'm completely lost as to how to fix it.

Example:

I set-up a site on the test url of "test.devcompany.com". So the first portal alias has that address. When launched it, I added a portal alias for www.sitename.com and set it up within IIS as well. But when someone accessed www.sitename.com it instantly redirected them to test.devcompany.com.

One site in question is www.koscvb.org ... it redirects to the dev site address of koscvb.imagegroupinc.com.

Any help would be GREATLY appreciated!

Thanks in advance!

I've cleared the cache in the DNN host settings. The IIS process has been stopped and started. The entire server has been rebooted. Etc. I'm not sure what else their is to clear?

The problem seems to be above the cache level though. IIS responds to both the real address and the dev address, yet when the real address is accessed it is instantly redirected to the dev address. It's happened two different servers...at different hosts, etc...no common code, one was configured manually, the other one-click installed using the host control panel. But both suffer the same issue.

Has no one else tried running DNN by installing it on a test URL and then moving it live by adding a new portal alias for the live site and configuring IIS to see the live site?

Any help would be awesome! This is a frustrating issue, and support for DNN seems horrid.