Hi,

I have a primary DNN installation on Network Solutions (NS) that works just fine. I am adding a Parent Portal using a domain name also registered with NS.

(Note: I've removed the "www" from each URL below to keep the editor from making links out of them)

1. The primary DNN installation is in the NS hosting account subfolder (mymainwebsite.com/site)
2. Using the NS control panel I pointed my new domain name (mynewsite.com) to the DNN subfolder on the hosting account (htdocs/site/)
3. In my primary domain I created parent portal alias for the new site - mynewsite.com/site
4. When I visit mynewsite.com I see the new home page, but no CSS is applied so the page is un-formatted.
5. Also, I noticed that there is no DNN / aspx in the URL when I first visit the new portal -- just the new domain name.
6. I was able to log in the portal and the browser is still  displaying with no CSS.

Looking at the page source code of the new site (with no CSS) from the browser shows that all requests for the various DNN components (CSS and such) include the /site/ portion of the URL path. I'm thinking that DNN might be doubling the sub-folder name ( /site/site/... ) when generating the URL code and thus the browser isn't finding the referenced resources. In fact, after clicking the max / min option for DNN control panel I get multiple occurrences of  "/site/" in the URL (/site/site/site/site/ etc).

Also, logging in the host account and editing the new portal by entering the portal alias as "mynewsite.com" without "/site" in the end and that just results in a redirect directly to the primary / host website.

Any suggestions to get this portal working?

Jim

Chris, thanks for reply.

To answer your questions:

1. I have two domain names. One domain name is used for the host / portal 0 and I want to add a new parent portal to this same DNN installation using the second domain name.
2. The hosting company does not allow DNN installations in the root folder on their shared servers. So, DNN is installed in a sub-folder named "/site/". I have a small index.htm file in the root folder that redirects to the "/site/" sub-folder (where DNN lives). So, I can get to the primary site using base domain name or by adding "/site/ " to the domain name. And the main site works fine.

Here's a breakdown what I've done until now (I hope it makes more sense than my first post  ;-)

I'll call the primary domain name: "mymainsite.com"
And the new domain name:  "mynewsite.com"
(I'm leaving the "www" off each URL to keep the Rich Text Editor from making a link)

1. I have a primary DNN website (host / portal 0) that has been up and running for about 6 months (mymainsite.com)
2. I want to add a new "parent portal" to this host account.
3. I have a new domain name for the new portal (mynewsite.com)
4. I revised the domain information at the name registar for the new domain name to point to the hosting space that DNN is setup in on the shared hosting server (DNN is installed in a sub-folder at /htdocs/site/)
5. I logged onto my primary DNN account using my host account and created a new parent portal with an alias named: "mynewsite.com/site"
6. When I navigate to the new domain (mynewsite.com) I see the site, but without any CSS applied.
7. Clicking on some links cause me to be redirected to the primary website (mymainsite.com) and other clicks result in an URL that has multiple "/site/" paths inserted into it (/site/site/site/site/ etc)

Here is the link to the new parent portal: www.centripipe.com if you want to check it out.

Thanks.

Jim

Nope. That just results in being directed to the primary domain.

The primary domain is pointed to the hosting server space root folder (/htdocs/) at the domain registery and traffic is being redirected to the /site/ sub-folder via an index.htm file located in the root folder. Do you think that might be what's causing the problem?

I can change the domain registery for the primary domain to point directly to the DNN folder (/htdocs/site/) if you think that might work. I just didn't want to mess the primary installation up...

Thanks again,