I am new to DNN and going through quite a few books at the moment.  I cannot seem to wrap my head around an issue and would like some direction from the forum.  I will begin by offering a project problem/scenario:
Let's say I wanted to build a real estate website as DNN site - this would be the main site.  I will have agents who can log in to the site.  I would also want to offer my agents the ability to purchase their own domain and I would setup a site for them that is exactly the same site and the main one.  If anything changes on the main site it would change on theirs as well.  The site just gives them a presence for their clients and personalizes a little.  I did not want to go child portal route of mainsite/newagentsite but am uncertain as to the best way to set this up and what to look for when hosting this type of installation.

Any help would be greatly appreciated.
Thank You
Jon

(hopefully this will not go through twice as first attempt failed on my end)

Thank you Robert for the reply.  My thoughts were headed in that direction and I will go the no "personalization" same site route.  The personalization for the agent will be their domain name.

As far as hosting scenario - if my provider allows for unlimited domains pointing to site and unlimited subdomains this should take care of my needs should number of agents rise, correct?

Thanks again - I have enjoyed reading and have learned a lot from the members here.

To add to this, something that can be extremely useful and easy to use is OpenWebStudio.

I've been using single configurations (ie modules) with different aliases needing that personalisation specific to the alias.  Just a matter of  'If [Alias,System] = www.abc.com' and you can add a template specific to the module, or a generic one with an 'Else' used.

That could probably cover all personalisation you would want - from enabling personalised skinning (can be applied as a skin object) to the content.