Set Up Domain Mapping When Your WordPress Multisite Network is on a Subdomain or in a Subdirectory

If you set up a WordPress Multisite Network on a server with other websites on it (for example, Lawyerist Sites is hosted on the Lawyerist server, so there are a number of directories on the server. If your network is set up similarly, you will probably get frustrated trying to set up domain mapping according to the “standard” tutorial by Otto on WordPress.

Here are a few problems I solved on the way to getting domain mapping working on Lawyerist Sites.

Install the WordPress MU Domain Mapping plugin

For installing the plugin, the directions at Otto on WordPress are spot-on. Just don’t try to install it the usual way, through the WordPress dashboard. It won’t work.

Directing the domain to your network

First, you need to point a domain at your network. The easiest way to do this is by setting up nameservers for your subdomain. In my case, I set up nameservers for, because it will be relatively easy to help our customers point their domains at our server from their registrar. Most will not actually have hosting, so we will simply set up email forwarding or set them up with a Google Apps account. (It would be relatively simple to redirect mail servers back to a customer’s server, if they want to host their own email.)

This seems easier than talking people through setting up A records or CNAME records. And if I ever need to move the server, I can redirect the nameservers without our customers having to do anything.

If you aren’t sure how to set up nameservers, consult your own domain registrar (for the domain you want to use as a nameserver). They should be able to help you do it, or do it for you.

Once you have set up nameservers for your subdomain, visit the domain registrar and update the nameservers for the domain you want to map to your Multisite Network. In other words, make sure your domain — in our case, — is using your nameservers.

Adding on a domain

Now, log into your server’s control panel (mine uses cPanel, so that’s what I’m used to) and add on the new domain. This is where Otto’s tutorial gets vague.

The key is to create an add-on domain and set the Document Root field to the same directory as your network’s installation directory. So if your WordPress Miltisite Network were installed on public_html/network, and the domain you want to map is, you would create an add-on domain for and put public_html/network in the Document Root field.

Mapping the domain

Now, you can pick up with Step 4 of Otto’s tutorial, starting at the third paragraph.

If, for some reason, you map the domain before updating the nameservers (or before the updated nameservers take effect), you may get some unusual behavior. It will go away as soon as the nameservers resolve, though, so don’t worry too much about it.

Published by Sam Glover

Sam Glover is the founder of, and likes to skateboard.

Join the Conversation


  1. Simple, great, and it worked for me. Have installed MU several times in the past, but today I just wasted 4 hours until I got this.

    Wished I had got this earlier, it would have saved those hours of surfing, reinstalling, contacting unhelpful support etc. The least I can do is link to your site, at least as a way of saying thank you and as a way of getting your page seen.

    Thanks Sam.

  2. Thanks Sam! “The key is to create an add-on domain and set the Document Root field to the same directory as your network’s installation directory” saved me.

    1. Thanks times two, Sam! My head was hurting trying to figure out why my domain mapping wasn’t working and it turned out to be the document root which was still set to the default upon addon domain creation.

      Funny how your 2013 post had the answer after reading all these newer articles!

Leave a comment

Your email address will not be published. Required fields are marked *