Mark, could you please elaborate?  We did just that.  We created a subdirectory called "BFD" off of the root of the DNN site.  (Did we create it in the right place?)  We have our domain working fine.  When we access http://www.MyDomain.com we get the DNN site as normal, but when we try to access http://www.MyDomain.com/BFD or http://www.MyDomain.com/BFD/index.html we get a 404.

Did we create the subdirectory at the right level?  We see other folders such as "admin" and "App_code" at this level.  Do we need to drop it further into the structure?  Do we need to set some security?

We also played around with creating a page off of the root then assigning "Advanced Page Settings" to look for the content.  We got it to work when we told the page to look for an external web page, but we do not want to do that.  We want to import it all into our DNN folder structure and use the one domain to manage all content.

Thanks in advance.

Keith

 

 

Hi Mark, I am using a Windows Azure Website server, DNN is one of the CMS options that you can get preinstalled there but in general it works like hosting my own webserver and I can use FTP, too. Regards, Tim

Tim - that may be an IIS setting and goes beyond my knowledge since I don't host sites. I'm afraid I may not be much help.

Keith - You can use an iframe to pull in other pages. It works but I can't say I'm a fan of doing so. You'll still need to host the HTML pages somewhere and have to maintain them.

Check with godaddy and see what they say about it because I know it can be done. I've done it a few times on my DNN intranet.

Mark