ns1/ns2 nameserver aliasing for wordpress multisites?

K

krystofo

Verified User
Joined
Jan 17, 2011
Messages
8
Hello. I am installing a Wordpress multisite and also participating in Wordpress.org forum discussions about DirectAdmin. Currently most Wordpress instructions are for Cpanel.

Wordpress multisite has a domain mapping plug-in that enables each sub-blog to behave as an independent website with its own .com domain. We have worked out the protocol for the DirectAdmin equivalent for Cpanel "domain parking" which is referenced in all "domain mapping" instructions. (See bottom of this message.)

However, all Wordpress "domain mapping" instructions suggest either "CNAME aliasing" or "ANAME aliasing." My question: Is there a way to do "domain mapping" using NAMESERVERS instead of cname or aname aliasing?

Thank you anyone. Here below is what we have already worked out for cname or aname aliasing.
  • Aname redirection requires IP numbers which can change if you change webhosting.
  • Cname redirection enables easy changing of IP numbers. However, Cname redirection causes problems for email services.
  • Using nameservers for "domain mapping" is possible. Wordpress.com uses namerserver-based domain mapping. I believe nameservers are more efficient than Cname or Aname aliasing. Also like Cname aliasing, you can then assign a new IP to the nameserver instantly. And like Aname aliasing, you can also enable email services. But how to do this? Is there some other HTTPD setting that might make "nameserver aliasing" possible for Wordpress domain mapping? That's my question. Thank you anyone.
  1. These instructions work for CNAME aliasing (yourdomain.com under "host records" at Enom) or ANAME aliasing (123.45.678 IP numbers under "host records" at Enom), but NOT for nameserver aliasing (ns1.yournameserver.com etc. under "DNS Server Settings" at Enom.)
  2. DirectAdmin -> Admin Level -> Extra Features: Custom HTTPD -> click on relevant primary yoursite.com domain name of your wordpress installation -> Add text below -> Save.
  3. For yoursite.com/subdirectory multisites add:
    ServerAlias mysubblogsdomain.com​
  4. For subdomain.yoursite.com multisites add:
    ServerAlias mysubblogsdomain.com *.|DOMAIN|​
  5. (Replace mysubblogsdomain.com with the sub-blog's domain name you want to map--not the primary domain.)
 
Last edited:
All nameserver aliasing does is point a different nameserver name to an IP#. Nothing else at all. I don't see how that's going to replace CNAME or ANAME records in zone files.

Jeff
 
nobaloney said:
All nameserver aliasing does is point a different nameserver name to an IP#...
Click to expand...
Thank you for the reply.

I do not understand DNS. Perhaps I used the wrong terminology. Perhaps I am trying to avoid altogether what is called "aliasing." Wordpress Domain Mapping instructions always refer to the choice of CNAME aliasing (using the domain name) or ANAME aliasing (using the IP number).

In an Enom account, setting CNAMES or ANAMES require using Enom's "public" or "default" nameservers, referred to as "our nameservers" under "DNS Server Settings" at Enom. To set CNAME or ANAME records, we then go to the "Host Records" section of an Enom account.

In contrast, in my experience, most webhosts ask the webmaster to submit "custom nameservers" under Enom's "DNS server settings." For example, Wordpress.com instructs premium bloggers, activating their own domain name to submit the following custom DNS server settings:
NS1.WORDPRESS.COM
NS2.WORDPRESS.COM
NS3.WORDPRESS.COM

Perhaps, instead of the above "custom nameservers" for DNS Server Settings--you could instead leave "our nameservers" selected--and then go to Host Records and submit ONE of the above nameservers as a CNAME record. But I don't think this works and if it did, I don't see the point. You would still have the problems of "CNAME aliasing" such as unreliable email service.

To summarize my points:

1. Wanted: nameserver-based domain mapping. This is used by Wordpress.COM. For domain-mapped Wordpress sub-blogs (giving each blog an independent domain name as if it were a separate website)--I would like to be able to use "custom nameservers" under DNS Settings at Enom. Presumably I would use the same nameservers for domain-mapped sub-blogs as for the main website. Then use DirectAdmin's HTTPD to attach the sub-blog domain name with the main site's domain name. The advantages are:
-- No problem providing email services.
-- Instantly can assign new IP numbers to a nameserver. No need to ask each sub-blog owner to submit new IP numbers.
-- Avoids using Enom's overloaded "public nameservers."
The problem is:
-- I do not know what DirectAdmin HTTPD settings might work. Nor am I certain this is possible. Wordpress.COM may be using additional programming, beyond the "domain mapping plug-in" which is readily available.

2. I do NOT want 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 suspect that the use of CNAME or ANAME aliasing is actually a type of domain forwarding, not a direct activation of a domain name.

3. I.e., I would like to do what Wordpress.COM is doing: use Enom's "custom DNS" nameserver setting to activate domains for "domain mapped" Wordpress sub-blogs.

I SUSPECT THIS MIGHT BE POSSIBLE WITH THE CORRECT HTTPD SETTINGS IN DirectAdmin...? Any suggestions anyone? Thank you.

If you still do not understand what I mean, but are interested to help, I would suggest browsing these pages:
 
Last edited:
Are you hosting on your server or on WordPress servers using your domain name? If on their servers, then point the entire domain name to their nameservers at your registrar and ignore your DNS settings on your server completely; perhaps even removing the zone file. But if you do that you'll have to ask them how to get email.

If on your server, then I have no idea what you need to do; perhaps someone else has set up WordPress multisite and will respond.

If you alias an entire nameserver you'll probably break resolution for all sites on your server.

Jeff
 
Hi Jeff. Wordpress.com does not offer hosting. Anyway, I have left the following inquiry: nameserver domain-mapping at the WP Plug-in Forum. Meanwhile, cname or aname aliasing is workable, just slightly less than ideal. As you say, if nameserver-based domain mapping is possible without sophisticated programming, perhaps someday someone will reply here or there. Thank you.
 
P.S. Well I do have a reply about nameserver domain mapping at the WP Plug-In Forum--from a lead developer of the domain-mapping plug-in! It looks as if I was simply not asking for the right thing. What I was calling "nameserver-based domain mapping" still uses CNAME or ANAME aliasing--but it seems the only difference is in where the nameservers + aliasing is hosted: at the registrar or at the server.

Also, after all this fuss, I have decided to remain with registrar-based aliasing for the time being. Even though this is less efficient, I believe it will work fine for small websites. Also, I prefer not to be responsible for email hosting. With registrar-based aliasing, the registrar then can tack on registrar-based email hosting for a small fee. Email forwarding also then can be done free by each client at his registrar, without needing me to fiddle with anything.

But it certainly is good to know that what I called "nameserver domain-mapping" probably IS possible and probably does not require anything special. I probably just need to ask my webhost how to do this. Perhaps DirectAdmin itself has instructions for setting up ANAMEs at the server level.

In any case, I now feel confident that "nameserver domain-mapping" probably is possible and I now know how to find the remaining instructions if I ever need them. Mission accomplished. Thank you again Jeff for your help.
 
Last edited:
You must log in or register to reply here.
Back
Top