Enabling multiple parent portals in dotnetnuke

[climber_1979]

Hi there,

Although I've had a catalyst2 account for sometime, it was been gathering dust until recently and I've just bit the bullet and installed dotnetnuke 3.2.2 on my hosting account.

The installation worked like a dream. I had anticipated there would be some file permission problems, but no - everything worked fine first time!! Thanks catalyst2 ;-)

This question is more of a configuration one. I would like to run multiple dotnetnuke parent portals under one hosting account, but I'm not sure how to do this. Let's say I have 3 domain names (registered elsewhere):

www.domainname1.com, www.domainname2.com etc

When a user goes to www.domainname1.com or www.domainname2.com this should point to my hosted domain at catalyst and should hit my DotNetNuke virtual directory (under the wwwroot directory). This should then redirect to the relevant portal, whether that is domainname1.com or domainname2.com.

How do I do this? Do I need to add another domain onto my hosting account? Would this be a subdomain or a domain alias (I'm not sure what each one means)

Has anyone managed to do this here and if so, would you be able to help?

Cheers!

[Jacob]

If you want them all to point to the same DNN installation then you will need to purchase domain aliases. If you want each domain to have a separate installation then you will need to purchase additional packages or additional hosted domains.

Regards,

Jacob

[climber_1979]

Jacob,

Thanks for the reply. I purchased a domain alias so that I can have, for example, domainname2.com pointing to myhosteddomain.com. This seems to be working fine.

What I'm trying to do is to get all requests to www.domainname1.com and www.domainname2.com to route through to the dotnetnuke installation, which is installed under the wwwroot directory. For dotnetnuke to recognise each site as a distinct parent portal, I'm creating a virtual directory for each site which point to the same physical dotnetnuke directory. However, I need to be able to map any requests to www.domainname1.com to myhosteddomain.com/site1virtualdirectory and requests to www.domainname2.com to myhosteddomain.com/site2virtualdirectory etc.

The domain name alias only lets you map an alias to the hosteddomain.com root directory, but not it's virtual directories, which I need.

Can you think of any other way I might be able to do this?

Cheers!

Alexis

[Jacob]

Hi Alexis,

Could you not have a script on the first page of the site that redirects according to the URL?

Regards,

Jacob

[climber_1979]

Hi Jacob,

Thanks for the tip. This is what I went with in the end - a default page in the root directory routing through the request, based on the request URL. Thanks for your help!

Cheers!

Alexis