Hi,

Just picking up on one or two things.

"the superuser and administrator for the default DO work in this domain -- which does not seem right" ... a Host (SuperUser) account will log you in to any portal, whereas Admin accounts only access that one portal. Regarding the Admin account, did you perhaps use the same credentials as the default portal when creating the Admin account for the new portal?

"i understand logging as host, but this is hosted on - godaddy – which is the “one button click” king – so I haven’t even seen the iis console and am not sure what the host header for iis should be or where to find it.  sorry...  may not be part of the issue here..." ... I think you're confusing your hosting account with GoDaddy with your DNN Host (SuperUser) account. I am not familiar with GoDaddy but they presumably give you a Control Panel (not to be confused with the DNN Control Panel) of some description in order to control your domain, that is where you will add your headers. I know there are some GoDaddy users on here, so hopefully they can supply more information. or you can enquire at GoDaddy.

"actually on closer look, the site that comes up at testsandbox.mydomain.com is the default website installed with the initial dnn" ... whenever you create a new portal, it will install the default DNN site unless you have selected a different template.

Hope that helps a little.

OK, you asked a GoDaddy guy to chime in...  Here goes...

GoDaddy and Portal aliases gets wierd.  First we need to get on the same page semantically.  In GoDaddy you have a domain unrelated to DNN that is your Primary ['hosting'] domain, which is the Root domain; call it Root.com.  You cannot install DNN in the root, so call the folder you install DNN to ... DNN.  The path to portal0 is www.Host.com/DNN

You can tell GoDaddy in Hosting Manager to map AnyDomain.com to Root.com/DNN. [portal0]. You MUST then put both AnyDomain.com AND AnyDomain.com/DNN as Portal Aliases or it will not work.   www.anydomain.com now works, as portal0

Now introduce a Child portal; call it Child.  It becomes, say  Portal 4.  The path to it becomes Root.com/DNN/Child.  the 'standard' alias is www.Root.com/DNN/Child.

Now...  GoDaddy lets you point a new domain directly to that child folder in the Hosting Console.  Call that domain PerfectName.com.  To get it to work you need to have PerfectName.com AND Perfectname.com/DNN AND PerfectName.com/DNN/Child as aliases for portal 4, in addition to Root.com/DNN/Child.  To see this in action, go to www.brooksfloors.com  look at the url in the address bar.  Click Home tab, look again.  Click Home tab again; look again.  The exact same page needs 3 aliases for the child.  The TRUE address is www.brookshardwoodfloors.info/asp/telford ...  It has to be an alias, too.  I don't make this crap up...

Last I recall checking, this applied to subdomains as well so for all to work you would need Child.Root.com, Child.Root.com/DNN and Child.Root.com/DNN/Child as portal aliases, in addition to Root.com/DNN/Child.

The smart thing to do on GoDaddy is to Forward and Mask PerfectDomain.com to Root.com/DNN/Child, and everything behaves like magic and you don't have to tear your hair out on portal aliases...  To see that in action go to www.stonycreekbuilderssupply.com .  EVERY page reports only the one base "preferred" domain name and only I care about the true one [in this case www.indianlake-pa.net/asp/sbs/ ]

It doesn't need to be this hard.  I'm not saying it's GoDaddy's fault, either.  I think the portal alias approach is great in concept but flawed in implementation unless someone can explain it better. 

Bob H

What you observe is what I get as well.  [Further, If the portal is a child portal, you have yet another layer in the url/path...]

If you purchase a domain [any domain; call it funcky.net] and make it your Primary hosting domain, your content would then reside at www.funcky.net/dotnetnuke60

If you then go to Domain Manager in GoDaddy, and change firstfriends.com to Forward to funcky.net/dotnetnuke60, with Masking...  
Then your url will ALWAYS be just www.firstfriends.com and nothing after it.

To see this in action first go to www.indianlake-pa.net/asp .  [This is the same as yours except asp vs. dotnetnuke60]  Poke around and watch the urls.

Now go to www.indianlake.info  Poke around and see that the url never changes...  Exact same site/content/instance...

The only way to get the dotnetnuke60 out of the picture yet still present 'reuseable' path info is to do a root install which GoDaddy will not allow.  [Every time somebody hacks it and tells somebody else how, GoDaddy pulls the plug...]

HTH,

Bob