Hi all,

I was wondering about how to make a node have its own subdomain.
Or rather a member (with a contents-node linked)...

The scenario is like this:
1) A visitor fills out a application form, posts it and a member is created.
2) Just after the member is created a contents-node is created at a given place in the node hierarchy. Some properties are set via code, and a reference to the contents-node is set in a property in the member-node.

Thats about it.
But...

I need to be able to access the contents-page created with {membername}.domain.com. What would be the best practice? The solutions i've been thinking 'bout is:
1) To programatically set a Hostname on the contents-node.
2) To let another instance of IIS handle a blank hostheader, redirecting all unbinded access to the umbraco site.

All registration functionality is located in a Usercontrol.

I suppose the 1'st alternative would be the best one, but for some reason i cant get a hostname-change working in the instance of the umbraco site (supposable cause of misconfiguration with other nodes with hostnames).
The member container is located under the startpage of the site (@level=3).

Anyone done this before?
What would be the solution?

What about a HTTPHandler with UrlRewrite? Should i even bother?


Thanks,
Anders

I'd say about thousands.
You'd say the choice of solution is depending on that?