I have one existing portal that works fine and now I am trying to setup another. I am unable to access new parent portal I have setup.

- I registered the domain name pointed the DNS
- I created a new portal in DNN with portal ID of 1 and gave the alias of the new domain
- In IIS I created a new site and pointed it to the directory with the default.aspx
- While in IIS I then added a host header for both domains

The dns  as propogated but I get "unable to access server" when browsing to the new domain.

Am I missing something?

Thanks, Justin.

If I understand your question correctly, you had the first instance of DNN running fine and then you wanted to add another portal. If that is the case, you do not need to create a new site, just add the host header of the new site to the same DNN site you initially had. What you did actually causes problems. Remove the new site in IIS, DNN, the one instance you had originally, will take care of sorting out what site it must render based on the host header. But for this to work, the host headers for all child portals must be defined in the same site as the core DNN site. Many people get confused about this.

Carlos

Asmussen:

Aha, the DNS error is another thing altogether. What I do to do testing when running DNN on either my laptop or a server is to define the domains in my Hosts file. If you want to connect to the various portals on your own PC then put the entries below in your Hosts file:

127.0.0.1 www.portal0.com
127.0.0.1 portal0.com
127.0.0.1 www.portal1.com
127.0.0.1 portal1.com

One more thing for this to work, make sure that the home directory for DNN is set to the actual directory where DNN is running from and not the directory above it. For instance, on my laptop, I defined the home directory of the DNN site to C:\Inetpub\DNN434 instead of just C:\Inetpub. In this way you never have to enter the subdirectory in the URL.

This works for me perfectly, including for development with Visual Studio.

Hope it makes sense.

Carlos