My scenario is that I have a main site and I want to offer my agents to purchase their own URL which would point to the main site but show their URL address.  I would want ALL urls to match the main site (parent) and if I made changes to text in the parent site I would want that change to take place on all URLs that I have set up.  This could potentially be 40-50 sites.  It looks like I can do this with aliasing is that correct?

My issue here is I would like for the main page to display personal information related to the URL that the user typed in.  So lets say the main site is agentsite.com and I have an agent who has purchase newagentsite.com, I would like for newagentsite.com to mirror agentsite.com (be the same site) with the ability to possibly add an image of the person who owns newagentsite.com.  Likewise when newagentsite2.com comes on board the image would be for that agent, so on and so forth.

Please let me know if I am on the right track with how to do this.  I first thought I needed multiple parent portals to do this and may still need to do that but from the standpoint of updating the main site and having that replicate to all of the agents sites it seems the alias option is better.

I hope this was not too confusing, thank you for your time and any suggestions you have.

Jon

Hello,

How much content and what type of content do you wish to display on your clients sites?

The way I would approach this is to setup a portal for each of your users, so that takes care of the URL issue.

On your main site, make sure that the content you want to duplicate on the other portals has an RSS feed.

On each users portal I would set up pages that display the RSS feeds from your main site.

This way any updates you make to your main site are then displayed on all of your portals.

This will also give you a lot of flexibility for the future where you can add as much custom content as you require for each of your users.

It may be worth looking at this issue where we cover RSS in detail:
Issue no 3

Once you have created 1 client portal, you can create a portal template from the clients portal, so when you get a new client you just have to apply that portal template, this will setup all of the pages with the RSS feed for you, so this will save you a lot of time configuring each portal:

• DotNetNuke and Multiple Portals
• How to create DotNetNuke Portals (Parent and Child)
• Portal Considerations (When to use Multiple Portals / Parent / Child or create a new DotNetNuke installation)
• DotNetNuke Portal Aliases
• DotNetNuke Portal Templates and the Site Wizard

That is how I would approach it, does anyone else have any suggestions?