tc_s1

I reactivated the WordPress MU Domain Mapping plugin on only one site as a test. It is now resolving all pages and assets as https://www.MyDomainName.com/pagename again, however it is back to being REALLY slow (~13 seconds again). Other sites resolve quickly (where the plugin isn’t active), but they don’t resolve in the proper format of course, as noted above. I don’t know what could be causing this. Suggestions?

PS – should have noted that with all plugins OFF there is also a huge speed improvement in resolving the domain name going to MyDomainName.com (PING was the wrong thing to outline above and I apologize b/c I likely confused the issue by throwing that into the mix).

So essentially I now, with all plugins off (including MU Domain Mapping) am now able to reach via browser both the MyDomainName.server.host.com AND and https://www.MyDomainName.com at about the same speed, both FAST. I am a bit confused as to how this is working with the plugin network deactivated though, as i thought is was necessary for these to resolve?

Thank you for the response. I am aware that ‘DNS is DNS’ per se, but as I have no prior experience with this plugin, wasn’t sure if there was perhaps any difference or experience out there with configuring one over the other in the plugin.

I used NSLookup both on the server via SSH and via client machines on different networks. All results resolve instantly (both MyDomainName.server.host.com and MyDomainName.com as well as just server.host.com) from all locations.

When I turn all plugins off and try to run an NSLookup on MyDomainName.com and on MyDomainName.server.host.com I get the same results as when the plugins were on, but when running a PING on MyDomain.com I receive a request timed out (expected with domain mapping plugin off).

I’m not really sure what this has proven other than the server’s friendly name, MyDomain.com, isn’t reachable with the plugin off unless going to it via MyDomainName.server.host.com (which also was expected).

Any further advice as to what may be the source of this issue?