Doesn't seem to allow mapping of new domains with WP 3.5 upgrade

Having somewhat the same problem.

Added the plugin to a 3.4 -> 3.5 upgraded installation of a WP network, and the A-Record forwarded IP I have pointing to the WP network (installed in public_html) no longer works. I just keep getting directed to a cPanel default page about server misconfiguration error.

Prior to installing the plugin, the A-Record forward worked fine. Currently blogs work only if I use the subdomain urls defined by WP network.

I tried reversing the plugin install and cleaned up WP database, but problem still persists. Can anyone tell if the plugin modifies some WP config (or other) files in a way that removing the plugin and its database entries is not enough restore the network?

Are there some changes needed?

It should work fine in upgraded installs.

@el-bee – When you get that default cPanel page the domain is not being sent to your WP install. Contact your host support to see why that’s not working.

When you get that default cPanel page the domain is not being sent to your WP install. Contact your host support to see why that’s not working.

Ron first up thanks for the swift reply!

It turned out that the hosting provider is strict (= dick?) enough not to allow external nameservers to be used. To make things worse, they didn’ even mention anything about this at first (had to milk the answer a bit). So eventually, once I swapped nameservers from my registrar to the hosting provider and parked the domain in cPanel, everything was fine.

Now then, going to go vote for Compatibility etc. on the plugin page ??

Thanks again!