Can DM use ns1.nameservers instead of cname/aname aliasing?
I have successfully activated the Domain Mapping Plug-in.
However, I would prefer NOT to use CNAME OR ANAME ALIASING, even though these are the standard suggestions at WordPress.ORG. Disadvantages:
— CNAME aliasing creates problems with email services.
— ANAME aliasing requires each blogsite submitting new IP numbers if the IP changes.
— To submit either CNAME or ANAME at Enom, it is necessary to leave “our nameservers” selected, i.e., it is necessary to use Enom’s busy “public nameservers.” I have been informed by a webhost that this is less efficient than directly submitting nameservers.
— Most webhosts (including WordPress.COM) recommend activating nameservers, not CNAME or ANAME aliasing. I suspect that nameservers are more direct.
I.e., I would like to do what WordPress.COM is doing: use Enom’s “DNS Server Settings” to activate NAMESERVERS for “domain mapped” WordPress sub-blogs. (As opposed to Enom’s “Host Records” settings for CNAME/ANAME aliasing.)
If you do not understand what I mean, please click here for WordPress.COM: description of nameserver-based domain mapping.
Is this possible with the Domain Mapping Plug-in? I suspect it might work, if I knew how properly to edit the HTTPD file in the Cpanel/DirectAdmin control panel. But I am not a programmer and do not even understand DNS very well. So far, nothing I try works. Thank you anyone.
- The topic ‘[Plugin: WordPress MU Domain Mapping] Can DM use ns1.nameservers instead of cnam’ is closed to new replies.