Using mapped domains, not subdomains, in network admin
-
I have a multisite network configured as a subdomain install on a domain x.com (so sub-sites by default would be accessible as a.x.com, b.x.com, c.x.com etc).
I’m using MU Domain Mapping to map the sub-sites to a variety of different domains a.com, b.com, c.com. (These domains are all set as the primary domain for their respective sites in the sub-site dashboards.)
In the *Network Admin* dashboard for the parent multisite, is there any reason *not* to replace the “Domain” for each sub-site with its primary mapped domain? (So for example, to replace a.x.com with a.com, so that site a.com isn’t actually aliased as a.x.com at all?)
I ask because I’m having some issues with DNS propagation of the x.com subdomains and this would be a temporary workaround.
- The topic ‘Using mapped domains, not subdomains, in network admin’ is closed to new replies.
