BeyondDomainingI'm running WordPress Multi-Site Successfully with Domain Mapping on Subdomains on a VPS at HostGator.
One by one, I've been migrating my standalone WP Sites into my new 'primary' MU installation. This has been working fantastic for about 7 sites so far. However, right now I have run into a problem that is baffling me.
Each of the sites that I am migrating over are from standalone WordPress installs that look like this http://site.com
When I migrate them over and do the domain mapping on the multisite installation, they still look like http://site.com
Up to now, this has been fantastic.
However, with this latest site, site wp_8_table_name, once I switch the DNS over to the WP MU server, and try to visit the domain name it starts redirecting me to: http://www.site.com instead of to http://site.com
This breaks the site and renders it unresolved. I know it is the redirect to: http://www.site.com that is causing the problem, because if I de-select Primary in the Domain Mapping for the new site in question, and visit http://site.primarysite.com and/or http://site.primarysite.com/wp-admin/ the pages resolve just fine.
But I can't figure out why http://site.com starts being re-directed to http://www.site.com only when i switch the DNS over to my Multi-Site install.
I have checked my HTACCESS file and there is nothing any there that would be doing this. NONE of the other seven sites I have migrated over into the new WP MU install is doing this (and they all started off as exactly similar standalone wordpress sites). And the site i'm trying to migrate over did NOT do this back at its original standalone / legacy install.
My only hypothesis at this point is that the problem lies in the CNAME config at the domain name registrar.
All the other 7 successful sites CNAME records are located at Moniker (my registrar) and look like this:
Host Type Destination
* CNAME primarysite.com
@ CNAME primarysite.com
www CNAME primarysite.com
subdomain CNAME primarysite.com
This was a part I was a little confused on in setting up my CNAME records. Its probably overkill for me to have set up 4 different CNAME records, but its worked perfectly for me up till now, so why change..
In this latest case, ALL the settings at my registrar are the same, the only thing different is that this time, the name is registered at Fabulous (a different registrar) instead of Moniker.
That is the only thing different that I can think of. And my hypothesis is that perhaps Fabulous treats my CNAME config overkill differently than Moniker does and is for some reason re-directing to the www ???
My only other idea for a "solution" would be to add the http://www.site.com name to my Domain Mapping. The problem there though is I don't want to lose the SEO I've built up at site.com. Also, I prefer everything to be clean and consistent, and I don't want to have one of my sites be an odd-ball site that is always gnawing at me for change.
Any thoughts on what's going on with the redirect to the http://www.site.com ???
