There's a piece missing in my understanding. Say I have two domains/websites. www.domainA.com & www.domainB.com These are two distinct IIS sites. www.domainB.com has the DNN instance installed in it. most probably in the root folder in the IIS site. I want www.domainA.com home page only (default.aspx) to be redirected to the DNN instance under www.domainB.com and to have DNN take over and always show www.domainA.com/.... when a user requests www.domainA.com. HOWEVER any other webpage on www.domainA.com is served as normal by IIS. Nothing to do with DNN. So if a user types www.domainA.com/store. That could be a physcial folder called 'store' under www.domainA.com root folder and it's some php store app. The standard way was to add www.domainA.com as an extra host header in domainB.com and create a portal alias called www.domainA.com. That's OK if the site is totally served by DNN, which is notmy case. So www.domainA.com IIS site will have its standard host header www.domainA.com. SO here are my questions: - How is the redirect done in www.domainA.com/default.aspx? I am guessing its some DNN tabid. What's the format? Is it something like www.domainB.com\tabid\55\... which is the DNN home page for www.domainA.com? - When I create a parent portal for www.domainA.com in DNN (which is under www.domainB.com), what portal alias to be used? I think there should be a relationship between the portal alias used and the redirect url used in default.aspx? I hope I explained my scenario properly. Salama |