For the last couple of months we have been migrating our current site over to DNN on a staging server internal to our development team.  What we would like to do is have our editors have access to the staging site to make changes via the Active Directory piece internally, but then also have a copy of DNN on our external webservers with no AD setup but using the same database as the staging server.

We've tested it and it seems to be working, but the issue that we keep running into are the paths being messed up on the external facing site.  Instead of being website.com/path they are coming up as staging/website.com/path.  Is this at all possible or are we trying to do something outside of DNN's limitations?

We have the staging server setup internally then two DMZ webservers that host our site load balanced.  On the staging server we have a process that checks for for any file updates, uploads, and changes then using robocopy pushes them out to both DMZ webservers.  The relative paths are the same for all three servers.

Generally we've found that any page updates will show up immediately after they updated, but the link paths on the external site point to the staging paths.