We are a community college that has used DNN version 04.09.02 to develop its new website. All work for the website has been done using DNN EXCEPT for its home page which resides outside the DNN database. The name of the development/production server is www2. The server is running Windows 2008 server and IIS7. The current (old) website resides on a server by the name of www. This server is a Windows 2003 server running IIS6.

As we were ready for launch yesterday, we created a cname record in DNS with another name for the current website server and that worked great. We have no problems accessing any of the current website pages using its new cname. For the new website in the www2 server, we created a cname as well in DNS by the name of www. When we attempt to access the home page (not residing in the DNN DB), it loads easily, fast and with no problems whatsoever. However, when we attempt to access any of the webpages created with DNN and that reside in the DNN DB with the www host as part of the URL, the browser doesn’t know what to do and loads a URL like http://localhost/?TabId=640, which leads into a “page not found” error. This issue is not found when using the www2 as part of its URL. Under that host name, all pages in the DNN db load fine.

I’ve done some research and attempted to look at port aliases to see if that could solve our problem but could not find them in the admin panel of the current version.

Any help would be greatly appreciated. Thank you.

 Thank you Bruce. It was a portal alias issue as you suggested. I also lacked the credentials to access the host account. All this has been resolved and now website responds normally.