This is real frustrating can some one help with this?







Here is my situation I have W2k8 R2 IIS 7.5 with DNN installed under Default website virtual directory \dotnetnuke I created a portal "Portal1" so path is \dotnetnuke\portal1 to get it displayed. My W2k8 is fully namaged server not shared hosted solution. I registered domain and create A record, problem I'm facing is that if I type in IE domain1.com I hit default IIS home page in the interim I created redirect.html page and made it default on IIS so domain1.com hit redirect.html and redirects to http://domain1.com/dotnetnuke/portal1... but this is not good solution 1) is slows down display of the portal1 home page 2) it shows full path. I asked this question before but advices I got did not work for me. How do I do this? 1) hide path in URL and redirect to specific portal in this case portal1







Here is one advice I received asking this question previously:







You would have to make sure that in IIS under bindings you added domain1.com



You add domain1.com in DotNetNuke Admin->Portal settings as an alias.







Did both, added domain1.com in bindings under Default web Site in IIS - didn't work



and Yes I have domain1.com, www.domain1.com, domain1.com/dotnetnuke/portal1 , www.domain1.com/dotnetnuke.portal1



nothing works I always hit default page of Default Web Site in IIS and if I remove my redirect.html I get error file not found







second advice I get is this







Your dnn install on domain1 is not root.  Further your desired portal is 1 not the default 0



Correct



I use GoDaddy for many sites, and GoDaddy does not support root dnn installs.  Supposedly you can hack it, but they don't support it.



I use GoDaddy to register my domains but I do not host there  A records, aliases still at GoDaddy



To accomplish what you describe on GoDaddy, I buy a meaningless domain, call it XXX.com. 



I have domain I'm not using so can do this



I make it the primary domain for the hosting account.  Your files would then reside at XXX.com/dotnetnuke and your target site at XXX.com/dotnetnuke/portal1



Since I do not host at godaddy that does not apply exactly to me but yes I can create A record and point my xxx.com domain to same IIS server so Yes my DNN files are accessible at xxx.com/dotnetnuke and target is xxx.com/dotnetnuke/portal1 I can access like this as long I add also xxx.com as alias tomy portal1 in addition to domain1.com so far OK



Make domain1 a portal alias for portal1 on your dnn instance (while logged in as host)



did that again in addition to xxx.com



Forward your domain1 to XXX.com/dotnetnuke/portal1



did that



GoDaddy allows you to map/assign any non-primary domain on an account to any folder under the primary from their console w/o having to fuss with the forwarding, though it works the same way...



I did forward my domain1.com to xxx.com/dotnetnuke/portal1 and I can do directly from this screen on godaddy.com do preview and see my page so godaddy can get there, but if I then do to IE and type domain1.com I get error document not found, not sure if this is timing issue and I have to wait until godaddy gets updated in dns but so far this is not working







it is so frustrating, I'm not sure what I'm doing wrong and how to redirect domain1.com to /dotnetnuke/portal1 and in addition to redirection hide this path



I'm new to DNN but I have deployed many costume website on IIS not base on CMS and never had such problems in fact to test something I created another website on the same IIS and bind it to another domain, created simple html page type it in IE and no problem IIS know base on binding that yyy.com is under another website.