On the contrary, it seems a policy issue, not a technical one.
Everything I'm reading tells me that WPMU can work fine with shared hosting, with simple, minimal and non-threatening changes to the httpd.conf file to set up virtual hosts correctly.
See http://mu.wordpress.org/forums/ for many posts on this. And see here: http://www.blogopreneur.com/2006/11/06/ins...anelwhm-server/ and http://photomatt.net/2003/10/10/wildcard-d...nd-sub-domains/
It's not an issue of wildcard DNS because a test of my existing subdomains shows that they resolve to the same IP, which can be checked here: http://www.kloth.net/services/nslookup.php
And given that I can create manually entries for the subdomains I want, I don't actually need DNS wildcards.
The issue is simply putting a few lines of code in the Apache configuration file. This is what needs to be added:
><VirtualHost {SERVER_IP_ADDRESS}>
DocumentRoot /home/{CPANEL_USERNAME}/public_html
BytesLog domlogs/{YOUR_DOMAIN}-bytes_log
User {CPANEL_USERNAME}
Group {CPANEL_USERNAME}
ServerAlias {YOUR_DOMAIN} *.{YOUR_DOMAIN}
ServerName www.{YOUR_DOMAIN}
CustomLog domlogs/{YOUR_DOMAIN} combined
</VirtualHost>
Importantly, this entry must come after any valid subdomain VirtualHost entries one may have.
As one coder said, in WPMU: "no real subdomains are created, and neither are there any subdirectories. The only reason why we needed to create wildcard DNS is because WPMU uses mod_rewrite rules to determine which blog you are referring to. This means, the installation of WPMU actually reads the whole blog address and uses that to query the correct posts from the same one database."
Why won't TCH do this?
Is there a good reason, when other hosting companies offering shared hosting facilities do?
Can we get an answer on this, TCH?
best wishes,
Dr Ian Douglas
http://brusselstribunal.org
http://powerfoundation.org