I know this is going to sound like such a newbie question, but seeing as I am one, I can live with that.

I have DNN installed (www.sitename/DNN), I can set up a site but for the life of me I can't figure out how to get it to "go live" for lack of better words.  What do I have to do to get the site to display when the user goes to www.sitename.com?  As it is now, all I have there is the EasyCGI "this the future home of" banner.

Secondly, once I get the above addressed, what's the procedure to create a second site and have a different domain name point to it?

Thanks!

Now you're getting into things I don't know if I have control of.  Making changes to IIS, would that not be out of my hands given that the site is being hosted by EasyCGI?  As I said, I am new to the whole DNN concept.  I paid for hosting at EasyCGI, they provided me with a DNN installation which I can now work within.  My question is, how do I get to the next step which is to take what I created and let it be publicly used.  I was under the impression that the www.yoursite.com/DNN was the development environment for the web site, which would mean that there must then be a way to take what you developed and "publish it" in some way to accessible to all.  I assume what you are telling me with the IIS changes would apply if I was hosting it.  What if I am not?

In step b) above you mention creating a blank database, dropping DNN files into another folder, etc.  Since I never did this in the first place (I assume this was done by the automated installation script that EasyCGI ran), what do I do given my situation?

Jeff, there is no doubt it's working.  I can go to www.sitename.com/DNN and the site builder comes up, what I need to know is how to set it so that users don't have to type in that extra /DNN.  All I want is the site to be accessible under www.sitename.com WITHOUT having to go to /DNN.  I checked EasyCGI and I can't find an option to install DNN into the root of the site, it always wants to go to /DNN, so that being the case, what can I change such that a user going to www.sitename.com will end up at the new site?

I can't believe that any user who uses EacyCGI hosting is forced to publish sites where the end user always has to go to /DNN.  There has to be an alternative.  There is likely a simple way to do this but since me knowledge in this field is minimal, I'm hoping there's a simple solution someone can point me at.

Thanks.