Hello,

I've read countless pages trying to resolve my issue and cant seem to figure out whats wrong.  I have a DNN site hosted on my webserver (www.domain1.com) , I create a new parent portal (www.domain2.com) both registered in DNS, both pointing to the same nameserver, both on the same IIS server, and both at the same IP. I cannot access www.domain2.com, though it shows in my helm control panel, I cannot browse to it, it goes to a _holding.htm page created by the panel, not the dnn site I created.  I can get the child portals to work, just cant seem to figure out how to get to a parent site. What am I doing wrong?

Thanks Ian,

You forced me to relook at the "intended path" and that led me on my path to resolution!  What I found is that the control panel creates a new directory structure for a new website.  I had to go into IIS, and manually change the "Home Directory" local path to the root of the DNN site.  This still didnt work as it was going to an old default.htm page I'd left there from an earlier time. I then realized that I also needed to move up the default content page of default.aspx (the default page for DNN) in the Documents tab of the websites properties,   Now everthing works as intended.  I hope I have spared others the countless hours I spent, Its strange how it all seems to makes sense after the fact  :-)

Mark,

You're very welcome - glad you got everything straightened out. Is this a hosting provider like GoDaddy that provides control panels of this nature? Is that control panel really just a different user interface on top of IIS? I haven't experienced anything like that before so I'm a bit curious.

Take care,

Ian