I saw a listing by Marianne on GoDaddy hosting, and was very interested because I am having some trouble getting my install to realize that it is at the root of my domain, and not in the folder on the hosting space that I put it in.  This has led to some inconsistent URLs.   Explanation: my main hosting is abc.com, dnn is loaded into a folder under abc.com, xyz.com has its root set at that folder, yet DNN thinks it is at xyz.com/foldername instead of at xyz.com.  Anyhow, I've tried to reach the forum content that Marianne provided, and every time I do, I get an error stating "cannot be null"  -- is this a prophetic joke about GoDaddy's dnn support or is there a problem with the forum app?  Is there anyone who has a clue what I can do to get dnn to realize its relative path is "/" instead of "/foldername"?

GoDaddy won't allow you to put dnn at the root of your hosting space, so I loaded it to a subdomain, but through the portal alias, which was set to have its root at that subdomain for the main hosting site.  Under that circumstance, GoDaddy's installation wizard does allow installation directly to the root.  However, after installation, the host settings page shows dnn's relative path at "/foldername" anyway.  So I can activate dnn by typing in the portal alias in my browser, and it loads up the portal just fine, but then if I go to log in all the URLs afterward start with "portal alias/foldername/ et cetera" because dnn thinks it is at /foldername.  I was hoping this was a simple database entry that I could go in and change manually (it is a read-only report in the host settings window) but I haven't been able to find it in the tables.  Note that I can't remove it using the header excision method in web.config because the ambiguity of the situation makes dnn hang up in what appears to be an endless loop until it times out and spews an error.  Any clues on how I can fix this?  I'm pulling out my hair and I was nearly bald already...  :(