Okay this is a bit strange of a configuration and wondered if anybody had seen or done something like this -

The plan is to have an external facing website and an internal facing version of the same site - basically two installs of dnn that point to the same database.

The internal facing website would only be accessable from within the network (ie certain ip addresses) and the external one from the Internet at large - the intenal version would use AD authentication to control editing rights to the sections of the website and the external version would have no way to login (to prevent hacking and messing around)

I have done a few experiments with two physical different installs pointing at the same database and it seems like this should work but wondered if anybody else had done something like this

Thanks I did that in my tests - now I am observing something strange and wondered if anyone had observed this in a standard install (could be a bug)

I have one portal alias as localhost/dnnlocal and another as ntser1new.ksde.org/newsite whenever I go to ntser1new.ksde.org/newsite I get redirected to localhost/dnnlocal (the only reason I can see for this is localhost/dnnlocal appears first in the portal alias list) - i wanted to ensure this was some screwup on my part and not a DNN bug