Let me recap how DNN and hosting go together:


3$ hosting plan:
DNN will probably run but as soon as multiple user log in/perform admin tasks at the same time. your memory usage will spike and your hoster will ask you to upgrade or cancel your contract.

=> use to host your family pictures


Decent shared hosting on win2000/ win2k3 without application pool isolation:
Your DNN will run fine, each copy of DNN adds 30-40 megs to the application pool. Some lazy webmaster of a site on the same server forgets to close his datareaders and runs long running tasks on the webrequest thread. => your site is screwed for an other mans lazy coding. Don't even mention all those sites running under the same user previleges.

=> use for the site of your local soccer team


Decent shared hosting WITH application pool isolation, win2k3 IIS6:
Your site gets it's own w3wp.exe running under its own user account. This is the way you want your DNN to run, high security and high performance. BUT each application pool needs its own copy of .NET  in the memory. In case of DNN, ALL of .NET => +- 100 Megs of memory for each application pool. Your host might try and bill you for both the *application pool isolation* AND *the extra memory* if so find another hoster. Applications shouldn't be limited on there memory usage, find a host with a fair usage policy on memory.

=> any business related site needs the security and performance of application pool isolation

Dedicated hosting:
The mother of all hosting options. The performance tweaks you can do in machine.config are endless and deserve there own site. But you can't afford it.

=> for when you will build the next myspace on top of DNN

---

Edit your Skin.xml and Container.xml files with:
Yannick's SXE