Situation: We are working with a bank that has a primary corporate identity website, and each bank branch has their own mini-website residing within a folder of the primary website. For example, www.corporatesite.com/bankbranch1 for one bank branch and www.corporatesite.com/bankbranch2 for a different bank branch. Currently you must use the full path to get to the website of each bank branch. These bank however wish to have their own domain names that resolve only their mini-website. Meaning we want www.bankbranch1.com to resolve the same as www.corporatesite.com/bankbranch1/.

 

What We Have Tried: We tried setting up IIS to point to the www.bankbranch1.com domain to the corporatesite/bankbranch1 folder, however we are receiving application pool conflicts. The application pool that binds to the entire www.corporatesite.com domain includes all folders, which is what it is supposed to do. We considered detecting the domain and setting up a redirect to the bankbranch folders accordingly, which is not good for SEO/ranking. Setting an HTML frame or iframe to have www.bankbranch1.com pull in www.corporatesite.com/bankbranch1, is also bad for SEO/ranking.

 

What We're Seeking: We're looking for a solution that would allow a single physical folder (inetpub/wwwroot/corporatesite) to resolve www.corporatesite.com, www.corporatesite.com/bankbranch1/ AND www.bankbranch1.com where www.bankbranch1.com is the same as www.corporatesite.com/bankbranch1. Then all in a manner that does not throw off the search engines. We also can't install the website in a separate folder for each domain name. Maybe it can't be done?? Using win2008 server, DOT NET 4.0, C#. Thanks in advance for your help!

Why you don't create ALIASES on your DNS?