To me it sounds like the wildcard dns is not working. To test, load an html file onto your main site or if WP files are still there, e.g. – http://www.domain.com/readme.html
Then try that with the subdomain – http://sub.domain.com/readme.html
If the subdomain url does not load the readme.html, then either the wildcard dns is not configured right or possibly the web server is configured wrong (e.g. subdomain mapped to another folder)
Thanks for that useful advice.
The wildcard was set up in c-panel – however, having read your suggestion I uploaded the html file and the subdomain didn’t load.
So…
I updated the DNS within c-panel to also include the wildcard: * A xxx.xxx.xxx.xxx (an A record to the same IP as the main site)
And for a short while it worked AND I managed to create a sub-domain WP site. So far, so whoopee.
BUT
I was suddenly locked out – and cannot access the wp-admin log-on page without being served a 401 authorisation required.
Could be a lock out on account of my trying to use two different user accounts in the same browser session? or a fault in htaccess leading to a redirect loop?
Thanks again for your feedback, jkhongusc
Could be a lock out on account of my trying to use two different user accounts in the same browser session? or a fault in htaccess leading to a redirect loop?
A 401 isn’t a redirect loop.
Did you set up htpasswd or anything weird like that?
A little bit of time is all it took. An overly sensitive host had misread the surge in activity and triggered a lock down. It automatically cleared an hour later and all is now good with the world.
Take home message for me is that it *might* be an idea in c-panel to manually set the DNS rather than solely add the *.domain.com wildcard in the sub domains form.
Thanks, folks.