I think partially answered my own question through testing...but I'm going to ask just to be sure.
Am I correct in my understanding that when using the Multi-Domain plugin, ALL sites created, regardless of which domain they are assigned to, are part of the same network?
So if I had:
wpnetworkA.com and domainB.com where domainB.com was added to wpnetworkA.com using Multi-Domain then:
* domainB.com is not actually a wp network but rather just a domain pointed to wpnetworkA.com; and
* if a user registered mysite.DomainB.com then the site would actually "reside" on and be a part of wpnetworkA.com (and have all wpnetworkA.com's features, IP, plugins, etc...)
* 'mysite' would be listed as mysite.DomainB.com under 'sites' on wpnetworkA.com
If that's the case, it raises another question...
Is there a way to use WHMCS MU Provisioning and Multi-Domain in conjunction to actually deploy sites on different networks? (ie: mysite.networkA.com or mysite.networkB.com), where each 'network' really was a stand alone wpmu installation?
I'm trying to figure out how I can best leverage these to let users select from multiple different networks at sign-up (each with private nameservers, dedicated IPs, Domain Mapping...and having features and plugins specific to a niche/vertical market).
I'm thinking that I may be over-complicating this by trying to integrate everything, and the way to do it may be either:
A) within WHMCS by creating a different Group for each network - which would give me a sign-up page specific to each network (niche/vertical market); or
B) ditch the multiple network idea and use Multi-Domains to do it on a single network (then use New Blog Templates to configure niche/vertical specific sites).
I would greatly appreciate any feedback and if someone could validate or clarify my understanding.