Call Us 203.687.6053

Blog with a focus on DotNetNuke news, tips and tricks, DNN SEO, and insights and opinions about the DNN community at large.

Creating a DNN Parent Portal

Posted by Tom on Friday, May 25, 2007 to DotNetNuke, DNN Tips and Tricks

This post was inspired by a question in the dotnetnuke.com forums and continues our “DNN for Beginners” series.

I am new to DNN and I am looking for instructions on installing one portal per domain name. These portals are independent of each other. I want them to use the same SQL Server database and use the same DNN code base (the same Dlls).

The ability to run multiple websites from one DNN installation has been touted by many as the number one feature over the years (especially in DNN’s infancy), even though I beg to differ. That’s food for another post though.

DNN allows you set up a second website or portal on your install as a “parent” or “child” portal. The only real difference is that parent portals have a unique domain name, whereas child portals run off of parent portals such as mysite.com/childportal.

To get back to the above question, here is how to create a parent portal. Login as SuperUser and navigate to Host | Portals. Here you’ll see a list of all portals running on this DNN install. From the action menu choose Add New Portal.

DNN Portals

“Parent” is checked by default as the Portal Type, so no need to change that. Next, enter the domain name the new site will live on into the Portal Alias field such as my-new-site.com. A word of caution. When it comes to parent portals, the “my-new-site.com” domain name must already point correctly to your DNN install, otherwise the parent portal creation will fail. Most hosting providers support multiple domains pointing to a single IIS website at no additional cost.

Add New Portal

The Title, Description and Keywords fields are optional at this point. You can always enter these once the new portal is up and running. You do have to choose an install template though. For this discussion let’s go with the default DotNetNuke template. I’m currently working on a post that will shed some more light on DNN install templates and how to create your own.

Up next are the Security Settings. Pay attention in this section, because the user you specify here will be the initial administrator for the new portal. Once that’s done, click “Create Portal” and if everything goes well, a “fresh” DNN portal will appear. First thing you should do is log in with the admin account you just created. After logging in successfully, you can safely assume that your new parent portal is alive and well.

Do you have anything to add? Feel free to do so in the comments. And if you like this post, consider subscribing to my full feed RSS or get blog updates by email.


Permalink Permalink      Comments 14 Comments      RSS feeds RSS feeds      Email updates Email updates

 

Comments

Comment By Vasilis on Monday, May 28, 2007 at 12:33 PM

A closer look into the installation templates will surely be very useful too! And not just for newbies :) Keep it up buddy!

Comment By Jeff Kershner on Sunday, July 08, 2007 at 4:00 PM

What does this mean:
When it comes to parent portals, the “my-new-site.com” domain name must already point correctly to your DNN install, otherwise the parent portal creation will fail. Most hosting providers support multiple domains pointing to a single IIS website at no additional cost.

Comment By Tom Kraak on Sunday, July 08, 2007 at 4:55 PM

Jeff - that means that the “my-new-site.com” domain name must point to your hosting providers name servers and a DNS entry must be in place to point the domain name to your website ... all with the goal of reaching your DNN install via my-new-site.com.

Let me know if you have further questions.

Comment By Jeff on Sunday, July 08, 2007 at 6:13 PM

So my doing a nslookup for my domain name: doorywebsolutions.com, I see that it resolves to my hosting account. Looks like step 1 works...

You mentions that a DNS entry must be in place to point the domain name to my website. Well, when I create a parent portal in DNN, is my website the the install directory to my dotnetnuke (www.azlocals.com/dotnetnuke) or do I need to point it to a sub directory in that installation?

Thanks for your fast reply!

Comment By Tom Kraak on Sunday, July 08, 2007 at 8:29 PM

Point all your domains to the root of your DNN install. DNN will sort it out from there.

Comment By Jeff on Sunday, July 08, 2007 at 9:51 PM

I have my www.doorywebsolutions.com mapped to my DNN installation directory (www.azlocals.com/dotnetnuke).

I created a parent portal for doorywebsolutions.

But when I visit www.doorywebsolutions.com, my browser just goes to www.azlocals.com/dotnetnuke.

What might I be doing wrong?

Comment By Dan Cernese on Tuesday, October 23, 2007 at 4:07 PM

same here!

Comment By Tom Kraak on Tuesday, October 23, 2007 at 4:19 PM

And you guys are sure that you added the domain name of your new parent portal as a DNN portal alias?

Comment By pucca on Friday, November 09, 2007 at 9:22 AM

how to point the alias(e.g. my-own-web.com) to your root(127.0.0.1) in XP? what file I need to update.
How to create a new portal template? Thank you so much.

Pucca

Comment By Tom Kraak on Saturday, November 10, 2007 at 10:55 PM

Edit your Windows host file to tie my-own-web.com to 127.0.0.1. See mvps.org/winhelp2002/hostsfaq.htm for more info.

The default portal template (DotNetNuke.template) is located in \Portals\_default. So just open that file in a text editor, make your desired changes and "save as" your own template.

Let me know if I should blog more about that process.

Comment By pucca on Wednesday, November 14, 2007 at 7:34 AM

Tom,
thank you for the information. I have new in the setup the portal in DNN. here is what I tried for the portal alias:
1. go the hosts file enter one entry
127.0.0.1 my-own-site.com
2. go to IIS control to set up
2.1 a virtual directory to my-own-site.com and mape to the real directory
2.2 right click the directory, go to the property ->directory security tab ->authentification control -> browse -> andd IUser and ASPNET user
3. bring up the DNN ->host ->protal -> alias=my-own-site.com custom the directory to the directory I set in the IIS.
But it idoes not work. Can u tell me what is the problem?

Can you paste more detail information one the portal template part. I would like to set up couple options templates(beside dotnetnuke) when I create a new portal. Thank you So much.

pucca

Comment By Tom Kraak on Friday, December 28, 2007 at 7:31 PM

Pucca - did you ever resolve the above?

Comment By Club1Ten on Monday, February 11, 2008 at 2:03 PM

I am trying to add a portal. I go through all of the steps as outlined above, but when I go to the new address, it defaults back to the primary portal. I can't find anywhere to access the new portal.

Comment By Tom Kraak on Monday, February 11, 2008 at 2:16 PM

Club1Ten - has the DNS been set up correctly, meaning “my-new-site.com” points to your DNN install?

Add a comment
Add to Technorati Favorites

Email Updates

Enter your email address below and find our blog updates in your inbox.