I'm more of a stackoverflow.com guy, but am running into something interesting. I'm developing an application which is going to be managed once it is published (hoping sometime early next year)...
My goal was to have http://domain.com as the brochureware site, and have http://client.domain.com/ as the host that the client logs into. The hope being that 1 client to 1 database, instead of all clients into a single database. makes scaling lightyears easier.. need to scale more, throw a few more servers into the farm.
From my extensive research, the best methods to do this happen to be using some sort of nameserver to host the "hosts", and then setup an iis box that can read the headers and pass it to the app, which can control the database connections, etc.
I was wondering... I know i can use WMI to programmatically control nameservers if everything is windows based, but is this the best method? Am I going to run into a ton of headaches? can someone suggest a decent configuration that can be used to handle this better? I'm bootstrapping the software, so I've got limited resources to get it off of the ground.