G’day Markp

Your problem looks similar to what I was struggling with a while ago.

I’m hosting at “re-invent” and there I do not have access to any host-side / dns setting, I therefore asked them to point my new domain name to the server.

Response from re-invent:
I have pointed your connieolle.com  domain to your root as requested.  Please make sure you have this domain name pointed to our dns servers:
ns1.reinventinc.com
ns2.reinventinc.com

Secondly, re-invent installs DNN in a “DotNetNuke folder in the root – not a direct installation in the root”, a setup that forces me to use a “response redirect” command already at one portal only.

I use an “index.asp” file:

Single Portal redirect, taking me to the DotNetNuke folder:

<% <BR>Response.Redirect "<a target=_blank href="http://www.mudgeerabahilltons.com/DotNetNuke/">http://www.mudgeerabahilltons.com/DotNetNuke/</A>"<BR>%>

Dual Portal redirect, which just adds “/DotNetNuke” to the Web-Browser address window.

You might need to replace "/DotNetNuke” with “/dnn” if that’s where your installation lives.

Good Luck              -          to be continued.

G’day again people!

When I stared playing with portals (pestering Lee Sykes with my stuff ups) I attempted to set up “parent portals” without having a domain corresponding to the portal name. It didn’t work.

I then, successfully, played with child portals; “www,originalportal.com/anyalias” – which worked fine.

When I hade the domain connieolle.com pointed to the site, I attempted to “redirect” to a child portal: “www,originalportal.com/connieolle” another failure.

Not until I created a new parent portal as "www.connieolle.com" did I manage to get the previous posted “response redirect” working – and it’s all seems OK now.

That was my story folks  -  hope it can save someone from the same messing around.

Cheers for now…

Ollep