It's not as easy as portrayed in this forum and documentation. I'm hosting a clean install of v07.00.02 on a GoDaddy dedicated virtual Win2008R2 server accessible through RDP. I've gone through the steps outline in http://www.dotnetnuke.com/Resources/B... and have read the Site Alias section of DotNetNuke 7.0.2 SuperUser Manual.pdf. I have several domains that were previously pointed to my DNN server IP address and verified through nslookup. The steps for configuration are:
1. Point, or verify, the domain names to the DNN server IP address in DNS - check
2. Set the bindings of the domains in IIS 7.5 to point to the DNN server IP address - check
3. Use DNN Host | Site Management to add additional sites to the instance - check
4. Add additional aliases as Canonical type as needed through Host | Site Management | Advanced Settings - check
5. Go to the site (this automatically occurs when you first create the new site) - FAIL
The IIS7.5-DNNv7 combo always defaults to the MS web root instance-template on all URLs configured and tested.
Also, when I click the browse webpage link in the IIS right panel, the programmed URL is http:/myipname/dnn. the browser starts to load the new site and then loads:
Server Error in '/' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /GettingStarted/tabid/123/mid/572/popUp/true/Default.aspx
Version Information: Microsoft .NET Framework Version:2.0.50727.5466; ASP.NET Version:2.0.50727.5456