I'm not exactly sure what you mean by "wrapper"? A search on google only led me to canada's domain.com wrapper service which seems to be a custom service they provide for get past the typical 24-72 DNS update period. Still a bit fuzzy on that. I will make a logical assumsion that "wrapper" simply defines the account built on the host for which all add-on and sub-domains are defined within.
i.e. 2 real domains, the primary, 1 sub and 1 addon would actually produce 4 listings in cpanel
primarydomain.com
subdomain.primarydomain.com
addondomain.com
addondomain.primarydomain.com
I assume what you are getting at is a "dummy" domain to be the primary so that all the real domains can exist neatly in folders and creating special .htaccess rewrites isn't necessary. This is basically what I was able to get my host to do without actually registering a dummy domain.
For example, if my real primary domain was:
myspecialdomain.com
and I had 2 sub-domains:
me.myspecialdomain.com
you.myspecialdomain.com
and I had 2 email accounts:
me@myspecialdomain.com
you@myspecialdomain.com
and then I had my host change my primary domain to a dummy domain of:
myfakespecialdomain.com
the resulting change for my existing sites was:
myspecialdomain.com changed to myfakespecialdomain.com
I had to create a new add-on with my real domain which created or in my case used by default the existing folder "/myspecialdomain.com/"
This also added what I assume you meant a wrapper within the wrapper of (auto subdomain that has to exist):
myspecialdomain.myfakespecialdomain.com
Also, my existing sub-domains became:
me.myspecialdomain.com became me.myfakespecialdomain.com
you.myspecial.domain.com became you.myfakespecialdomain.com
I was able to add the real sub-domains back on now that my real add-on domain existed and then delete the XXX.myfakespecialdomain.com for the 2 sub-domains only having to still keep the:
myspecialdomain.myfakespecialdomain.com
and finally, my emails changed:
me@myspecialdomain.com became
me@myfakespecialdomain.com
and similar for the
you@myspecialdomain.com would become
you@myfakespecialdomain.com
In this case, I had to login to the existing "changed" email accounts and forward all mail I wanted to keep to newly created:
me@myspecialdomain.com
you@myspecialdomain.com
In my case, I think the 302 I had setup would have worked but the CMS I used wasn't written the best way and always exposed to installed folder when generating links thus making all links look like:
http://www.myspecialdomain.com/myspe....com/index.php
So the lesson learned in this scenario, before I setup a new host, either:
1) Work with them to see if they can accomomdate a "fake/pseudo" primary domain that can be setup before any applications, sub-domains and email addresses, then setup my "real" add-on domains, etc.
2) Register up a throw-away domain and use that as the primary domain (slightly wasteful)
3) Be wary of the applications I will be using for the primary domain and use .htaccess re-writes to 301 or 302 redirect to the folder I will have my primary domain application installed.
Thanks for all the input.