Hi Lori,

Hopefully you were able to resolve this issue. If not, then please see the instructions below.

As for the FrontPage extensions, they do need to be removed. Since it takes the Virtual Directories with it when removed, you may need to recreate them in the Hosting Control Center.

I hope this helps you out!

Regards,
Alicia R.
Go Daddy Hosting

Domain Alias

1.      Navigate to your Hosting Control Panel

2.      Click on Domain Management

3.      Create a new domain alias.

a.       Enter the Domain information into the fields provided.

b.      Enter the location as the folder that your DotNetNuke installation occurs at.

c.       Click create

d.      Wait for the Domain Alias to be created. 

This will create a new entry into the Host Name Headers property in IIS and point your domain to the folder location that you have chosen

Example:

Current Domain: MyDomain.com

DotNetNuke Installation:  MyDomain.com\DNN

Alias Domain: MyAlias.com

Alias Path: \DNN

Portal Creation

1.      To create a portal in DotNetNuke, the user must be logged in as the super user of the account with access to the hosts menu item.

2.      Click on the hosts menu item and portals sub menu item.

3.      In order to create a new portal one or more templates must exist to pre-populate the portal with data.

a.       Click Export template from underneath the portal listings

b.      Choose the portal from the drop down menu that you wish to create the template from.

c.       Enter all required fields to name and describe the portal template

d.      Click create to finish the process.

4.      This will take you back to the portals page.  Click Create Portal now.

5.      Enter information about the portal into the required fields and choose a template from the drop down menu.

6.      Click the Parent Radio button.

7.      In the portal alias field enter the name of the domain that you want aliased to this location followed by the path to the DotNetNuke installation.

8.      Click Create

Example

Current Portal: MyDomain.Com\DNN

New Portal Alias: MyAlias.com\DNN

Note: When you navigate to MyAlias.com in your browser you will now see your new portal and http://MyAlias.com will be in the navigation textbox in your browser.  It’s important to note that the way DotNetNuke resolves the alias, you must append the root folder path to the alias domain in your DotNetNuke portal creation. If not, DotNetNuke will be unable to resolve the alias and will return you to the default portal.  If this happens go back to the portal editing page and edit your portal alias.

There is some good information in this post.  I was really digging hard to try and find information on what I needed to do and came accross a lot of posts saying that I had to move the install to root.  However, I put a lot of time and effort into my first portal and I didn't want to screw with it.  Moving the install was going to be my last resort. 

I went to the Hosting Control Center >> Content >> File Manager.  I put a Check in the box next to [Root] then clicked on Permissions in the menu bar above the folder listing.  Put a check next to Write and then click OK.  I went back to my main portal, logged on as host, and then followed the directions in this post creating my parent portals.  It is up and running.  I went back and un-checked Write in the file manager when I was done. 

Hi Paul

I had the same problem. But resolved quickly.

When I created the portal, I put the alias as "mydomain.com/path-of-dnn".

And it access correctly if I type in the browser for the domais without the www.

Then I go back to portals, then edit my new portal. On portal aliases, I adde the alias "www.mydomain.com/path-of-dnn"

Now it work for but forms of the domain: with and without the www.

But I see that the cache (or history access) of the browser can give the result that we don't want. My browser (firefox) is still pointing the domain to their old folder in the server. But when I opened the domain with Explorer (that never have opened the domain before), this works.

Well, my english is not so good, but I think that you can catch the explain.