I was just wondering if having one install for DNN and running client (paying customers) under that one install is safe and recommended. If not, what is the point of having multi portal? (Many domain names, customers, using one install of DNN, with parent portals (sites)).  (This works for me just fine, but it is SCARRRRYYYY to think if a client does something, does the WHOLE (all) DNN sites go down?) ....or.. does anyone have any whore stories of something the client keeps doing and crashing their portal, and thus, ALL Portals on that DNN install ?.... and what Hosters can do to stop this? (Besides each client having their own DNN install and separate db????) If this is so, how does the Host banner add work? You’d have to recreate them on each install of DNN, and many other features would seem not to work.... or must be recreated on EACH install...

I’m just asking because as a hosting provider (small for friends and family as of now), is there something hosters should look out for? Limit the clients to? Stop them from doing? ...

Any good papers on how to setup parent portal permissions? the key items to check or limit, not just how to set it up. I know that . thanks.

thanks in advance!!

Chris has a good idea and that's I set up the sites that I host. In theory there's no reason why you can't have them all running under the same app pool etc. and, in theory, it should work flawlessly. I say "in theory" because you never know what the end user is going to do and it's not necessarily the actual client. Under DNN 2.xx I had one of the site running a forum and a user posted something that brought the whole install crashing down. I can't remember exactly what it was at the moment but do know it wasn't malicious. I think it was something as simple as trying to post a link using the PHP forum tags. I do remember that it took me a couple of hours to sort out exactly what happened.