This guide explains the features available in the Domains manager of the WPMU DEV hosting dashboard and includes instructions regarding:

  • Locating domain information
  • Adding domains to WPMU DEV hosting
  • Setting a primary domain
  • Locating and editing DNS records at several popular registrars

Use the index on the left to quickly locate usage guidance on specific features.

Not Hosting with WMPU DEV?

If you haven’t set up your WPMU DEV hosting account yet, visit WPMU DEV Hosting and explore the features of our best-in-class WordPress managed hosting, see pricing packages, and start a free trial.

Location

The Domain manager for any hosted site can be accessed from that site’s dashboard, first by clicking the Hosting tab and then clicking the Domains tab.


domain tab hosting dashboard

3.1 Domains

Link to chapter 1

The domains associated with the current site are displayed at the top of the domain manager. If you have not yet added a custom domain, the temporary domain you created may be the only domain listed.   If in doubt, temporary domains are those with the suffix .wpmudev.host,  as in:  yoursitename.wpmudev.host.

Next to the domain list, you will find:

  • DNS Status – A green checkmark indicates that the DNS has been verified.
  • SSL Status – WPMU DEV automatically installs an SSL certificate once the DNS has been verified. A green checkmark indicates that the SSL has been verified as well. Read more about SSL in the SSL, TLS & HTTPS section of this guide.
  • Primary – The Primary Domain is the main URL site visitors will use to access your site. A gray checkmark will display next to the primary domain.
    • To set a new primary domain, first, add the domain as covered in the Adding domains secton of this guide, then click the Set as primary option next to that domain.
    • Use the trashcan icon to delete a connected domain. The delete option is not available for the primary domain or the .wpmudev.host domain. All sites must have a primary domain at all times, and the .wpmudev.host domain cannot be deleted because it serves as the internal ID for that site.
    • To delete a domain set as primary, first choose a new primary domain and then delete the old one.

    Click the information tags for quick tips and links to more information.

    Hosting domains info button

3.1.1 DNS Records

Link to chapter 1

A DNS record is a database record used to map a URL to an IP address and serves to tell the entire internet universe– individual users, search engines, bots, and email providers– where to find your site.  If WPMU DEV is your host, then those records must by updated to point to our hosting.

Editing DNS

Editing DNS records is not difficult, but it must be done correctly or browsers may not be able to find your site. When the times comes to edit those records, it may be helpful to have this document open in a separate tab or in split-screen, so you can to refer back to it as you follow the steps to update your DNS records. Also, take advantage of the Registrar guides located at the end of this document to help you locate and edit your DNS records quickly.

DNS records, typically, are maintained by the provider from which you purchased the domain, and must be edited on that provider’s website.

The DNS records for each WPMU DEV hosted site are located below below the current site’s domain list. When you’re ready, replace the DNS records at your registrar with your new WPMU DEV records.

WPMU DEV DNS records location

The records you will be working with include:

  • CNAME – A Canonical Name or CNAME record is a type of DNS record that maps an alias name to a true or canonical domain name. CNAME records are typically used to map a subdomain such as www or mail to the domain hosting that subdomain’s content. For example, a CNAME record can map the web address www.example.com to the actual website for the domain example.com.
  • A record – An A record maps a domain name to the IP address (Version 4) of the computer hosting the domain.
  • AAAA record – A records are used for conversion of domain names to corresponding IP addresses. IP Version 6 Address records (AAAA) (also a quad-A record) specifies IPv6 address for given host. So it works the same way as the A record and the difference is the type of IP address. This record should be used in addition to the A record, wherever possible, as it represents the best practice and might even lead to performance improvements.

We recommend using the CNAME record whenever possible. Contact your registrar for support if you are unable to add or edit a CNAME record.

Need Help Editing Nameservers?

If you need help editing your namerservers, see our Changing your nameservers guidance, which includes links to DNS documentation for several popular registrars.

3.1.2 DNS Setup Tips & Troubleshooting

Link to chapter 1

Here are a few tips for working with your DNS records:

    1. When given the option, always change TTL (time to live) to as low as possible.
    2. Don’t change any other settings that may be in your DNS – such as for email or otherwise.
    3. Use a DNS Lookup service to see if it matches what you see under your Domains tab in the Hub.
    4. Should you ever have problems, screenshots of your full DNS settings is the best way for our support team to diagnose problems.
    Registrar guides

    To help you configure your DNS records we’ve created setup guides for some of the most popular domain registrars. Expand the Registrar guides index on the left to locate your registrar when your ready to update your DNS records.

3.2 SSL, TLS & HTTPS

Link to chapter 2

Secure Sockets Layer (SSL), and the newer Transport Layer Security (TLS), is a security technology that establishes an encrypted link between servers, browsers and mail clients.

Generally speaking, sites without a valid SSL are considered potentially unsafe, so WPMU DEV requires and provides SSL certificates for all our sites.

Therefore, all WPMU DEV sites use the https:// protocol, and not the deprecated and largely unsafe, http:// protocol.

Here are more detailed explanations of SSL, TLS, and HTTPS:

  • SSL – (Secure Sockets Layer) The standard for keeping an internet connection secure and protecting sensitive data that is being sent between two systems. It prevents hackers from seeing or changing any information being transferred.
  • TLS – (Transport Layer Security) The updated, more secure, version of SSL.
  • HTTPS – (HyperText Transfer Protocol Secure) HTTPS is what is in the URL when a website is secured by an SSL certificate. Details about the certificate can be viewed by clicking on the lock symbol next to the URL in the search bar.

3.2.1 SSL, Custom and Wildcard Certificates

Link to chapter 2

When a new domain is added, we automatically provision and install a free SSL certificate from Let’s Encrypt.

For most sites, SSL certificates will be applied in a matter of minutes, but the process can take hours or, in rare cases, a full day, depending on how quickly your DNS settings propagate around the world.

We renew these certificates automatically every three months.

As soon as the certificate is added to a site, we force all traffic over HTTPS only.

3.2.2 Adding Custom Certificates

Link to chapter 2

A feature to allow members to add custom certificates on their own is being developed, but until that feature is ready, our support team can help add custom certs.

First, you will need to submit a Certificate Signing Request (CSR) to a Certificate Authority. Certificate providers, typically, have tools or will assist with generating the CSR.

You can also use a free service like csrgenerator.com. When you obtain the CSR, be sure to save a copy of the Private Key.

Use the CSR to purchase the SSL certificate, which will provide you with the following required information:

    1. Private Key (created during CSR process)
    2. Certificate
    3. Certificate chain

Your SSL provider should be able to provide you with those if they create a CSR using their interface.

You can start a live chat or create a support ticket to provide us with the information.

3.2.3 Wildcard Certificates

Link to chapter 2

WPMU DEV provides free wildcard SSL certificates for both subdomain and subdirectory multisite networks. This means that even if you have a subdirectory multisite, you can map subdomains to subsites in it, and have them all covered by the same wildcard certificate. See the Notes for subdirectory multisite section below for more info on that.

Recommended Reading

Read our blog, Free Wildcard SSL for Multisite Subdomains, for a guide to setting up Wildcard SSL Certificates on your subdomain-based multisites.

Note that a subdomain multisite can be developed without a wildcard certificate, but if you take the network live without one, your subdomains will show a security error when visitors attempt to access them.

Generating the wildcard certificate

To generate a free wildcard certificate, you need only add a single record to your primary domain’s DNS and then recertify the SSL.

In your Hub, click the Hosting tab, followed by the Domains tab.

hosting dashboard domains tab

When you hover your mouse over the the green check icon in the SSL Status column for the temporary wpmudev.host domain of your site, you’ll see it automatically has a regular SSL certificate issued for it.

Hub 2.0 showing regular SSL certificate issued to a domain

When you hover your mouse over the icon for the custom domain you have added and want to use as the primary domain, you’ll see it too has a regular certificate automatically provisioned. But there is a prompt there to remind you that if you want to use a wildcard certificate instead, you need to add the required CNAME record to your domain’s DNS records.

Hub 2.0 CNAME prompt for wildcard SSL certificate

Once the required CNAME has been added to the domain’s DNS, you’ll then need to click on the Recheck Acme icon for the system to automatically verify the DNS and generate the wildcard certificate for your domain.

Hub 2.0 recheck acme for wildcard SSL certificate

To get the info you need to add to your domain’s DNS, scroll down to the bottom of the screen to find the site’s DNS records. Locate the CNAME (optional for wildcard SSL certificates) record, which has two parts: a hostname of _acme-challenge, followed by the actual record.

DNS info needed to enable free wildcard SSL certificate on WPMU DEV hosted multisite

The hostname and the record must be copied to your DNS. If your DNS is connected to the Hub 2.0 DNS feature, follow the guidance below to quickly update your DNS.

If your DNS is managed elsewhere, most commonly your domain registrar, then see the Registrar Guides section of this document, where we have compiled DNS guidance for several popular providers. If your provider is not covered, check with your registrar for help editing your DNS.

Using WPMU DEV DNS panel

Click the DNS tab at the top of the page to open your Domains list. Click the domain that serves as your multisite’s primary domain to view its DNS records.

dns site list

Click the Add button to add a new record and select the CNAME Record option.

add a new dns record

Copy the Hostname value shown on the Domains tab for your site and paste it in the Hostname field for the new CNAME record in the DNS panel. Copy the Record value you see on the Domains tab and paste it in the Is an alias of field. Click the Add button to save that new CNAME record.

CNAME to enable free wildcard SSL certificate on WPMU DEV hosted multisite

Allow a few minutes for the DNS change to propagate and click the Recheck Acme icon as noted above. You should then see that the custom domain now shows SSL as being secured by a wildcard certificate, and you can set it as the primary for your multisite.

Hub 2.0 showing wildcard SSL certificate issued to a domain

Now, when you load any subsite in your multisite, you’ll see that it too is secured by the main domain’s SSL certificate. In other words, all of these would now be secured by the same wildcard SSL certificate in either a subdomain-based or subdirectory-based multisite:

mainsite.tld
subsite.mainsite.tld
mainsite.tld/subsite

Notes for subdirectory multisite

As noted above, you can have a free wildcard SSL certificate automatically provisioned for your primary domain, even if your multisite is subdirectory-based.

Once the wildcard certificate has been added to your primary domain, you can then map subdomains to subsites in your multisite, making it look as though your multisite is actually subdomain-based. You can even have both subdirectory and subdomain based subsites in the same multisite in this case.

For example, let’s say the main site of your subdirectory-based multisite is:
mainsite.tld

You could have a normal subsite located at:
mainsite.tld/subsite1

And another subsite, in the same subdirectory multisite, located at:
subsite2.mainsite.tld

Both of those subsites would be secured by the same wildcard SSL certificate issued to your primary domain, and you don’t even need to register any additional domains to get it done. Here’s how to set that up:

You’ll first want to ensure that a regular wildcard CNAME record exists for the temporary wpmudev.host domain name of your site. If it is not already there, add it as follows:

  • Hostname – Should be just an asterisk: *
  • Value – Should be the temporary domain name of your site.

Wildcard CNAME record for subdomains

Once that is in there, go to the Domains tab of your site in your Hub, click the Add Domain button, and add the subdomain name you want to use for one of the subsites in your subdirectory multisite.

Add a subdomain to an existing subdirectory multisite

Then all you need to do is domain-map that site name in your WordPress multisite. In your multisite’s network admin, go to Sites > All Sites and click the Edit action link for the subsite you want to map to the new subdomain you just added. Under the Info tab there, change the Site Address (URL) to the URL of your subdomain, and click Save Changes.

Domain map a subsite in WordPress multisite

Now, if you visit your new subdomain URL in your subdirectory multisite, you should see it loads just fine and is secured by the same wildcard certificate that also secures the main site and all other subdirectory subsites. You’re welcome!

3.3 Adding Domains

Link to chapter 3
Have You Created Your Temporary Site?

If you haven’t created your temporary WPMU DEV site you should do so before proceeding. See Creating a New Site if you need help doing so.

Adding a site to WPMU DEV usually is a four-part process:

  1. Create a temporary site
  2. Add an permanent domain
  3. Edit DNS Records
  4. Set the primary domain
Migrating Existing Sites

If you are moving an existing site to our hosting, go ahead and create a temporary domain, then see our guide to migrating an existing site, which guides you through using the Migration Tool, by far the easiest way to add a site.

3.3.1 Add a Permanent Domain

Link to chapter 3

From the Domains tab for your temporary site, click the Add Domain button.

Hosting overview add domain button

In the Add a Domain popup, enter the domain name you would like to point to your site, omitting the http:// or https://. You must own the domain or have access to its DNS records to add it.

Add a domain popup

Notice the option to also add a www version of the domain. While www is no longer needed to access http and https domains, some users continue to use it. If no www version of a site exists, it is possible that these old-schoolers will be unable to find the site.

The new domain will appear in the domain list along with any other domains associated with the site.

Set a new primary domain

Once a domain has been added, our servers will automatically try to locate the site’s DNS, and then to create and add its security certification (SSL). These efforts will fail, however, until the DNS records at the site’s registrar have been updated to point to WPMU DEV servers.

The image below shows a domain that has been fully configured, indicated by the green check marks, and a site that has been added but for which the DNS records have yet to be properly updated.

new domain in hosting list

3.3.2 Set primary domain

Link to chapter 3

Once you add your permanent domain name, update your DNS records and the DNS Status and SSL certificate have successfully propagated, you should set the permanent domain as the site’s Primary domain.

Our system will automatically check your DNS configuration and will notify you via email once DNS resolves and the SSL cert is validated (both DNS and SSL are needed before you are able to set your permanent domain as primary).

Remember to be patient with DNS propagation. This usually takes, at least, several minutes, but can take hours and, in rare cases, a day or more.

When your DNS and SSL statuses propagate, indicated by green checks, you can set that domain as Primary by simply clicking Set as primary.

3.3.3 Removing a www domain

Link to chapter 3

If you added a domain with the www protocol to your Hub, chances are it’s not being used. WPMU DEV hosting automatically removes unused www domains from a site’s domain list shortly after a new primary domain is set, usually within two weeks. If the www domain does not disappear from your domain list automatically or you want to remove it immediately, the following short procedure will make that happen:

    1. On the Domains screen of the site’s Hosting Dashboard, locate the Set as Primary option next to the www domain you wish to remove.
set as primary
  1. If the www domain has been unused for an extended time and has not been automatically removed from the domain list, then it is probably not responding to the system’s attempts to remove it, and it is possible that the remove domain button (trashcan icon) will not work. Click the trashcan, and if domain is not removed from the list, proceed with the next steps to resolve the issue.
  2. Click the Set as primary option next to the www domain and allow a few moments for DNS to propagate. Proceed when the green checks appear, indicating full propagation, and a success notification appears indicating the new primary domain is set.
  3. Next, return the permanent domain back to primary status by clicking the Set as primary option next to it, then wait for propagation and the success notification. At this point, the www domain should no longer appear in the domain list.

If you encounter trouble removing a www site from your domain list, don’t hesitate to contact our 24/7 Live Support.

3.3.4 Multisite Domain Mapping

Link to chapter 3

When you map a custom domain to a subsite in a multisite install, you must edit the domain’s DNS to point it to the multisite IP address, and add the domain to the Domains tab exactly as you did for your primary domain above.

PRO TIP

If you use the WP-Ultimo plugin for domain mapping subsites, you do NOT need to add the domain to the Domains tab yourself. The plugin handles that for you automatically via its API when you add a domain alias to any subsite in that plugin’s settings.

3.4 Registrar guides

Link to chapter 4

This section provides guidance on editing the DNS records for several popular registrars, but don’t worry if your registrar is not among the guides below. Most registrars are similar in the way they organize their domain screens. Choose one and see if you can use it to guide you through the process.

Otherwise, your registrar may have a DNS Management guide available on their site, and you can always contact our Support Superheroes for assistance.

3.4.1 Cloudflare

Link to chapter 4

Cloudflare’s network includes 155 data centers around the world where customers’ websites and any static resources are cached and delivered to visitors from the closest possible server, dramatically reducing latency.

CloudFlare offers a basic free plan that includes impressive site performance, board security protection and powerful stats about your visitors. Plans start at $20 per month for your first website and $5 per month for each subsequent website.

Traditional DNS configurations connect your domain directly to your host, in this case WPMU DEV, and your site’s visitors access your content by interacting directly with the host servers. A Cloudfare configuration, however, is different. Instead of connecting your domain to WPMU DEV, you will connect it to Cloudflare, and in a separate series of steps you will tell Cloudflare where to find your hosted content.

Once configured, Cloudflare will begin pulling your content from our servers and caching it securely across it’s worldwide network. Your site’s visitors never actually connect to your host, but are served content from the cached copies on the Cloudflare network. The graphic below illustrates this configuration, and the security benefits should be readily apparent.

Cloudflare data flow diagram

If you haven’t already done so, you will need to create a Cloudflare account before proceeding.

Set the SSL

After creating your Cloudflare account, the first thing to do is connect your site to that account. Before we get into that, however, we need to highlight an important security configuration. This step takes place after your site is connected, but we’re pointing it out first to minimize the risk that members might overlook this critical step.

Once your site is connected to Cloudflare, you must set the SSL settings for that site to Full (Strict) under the Crypto tab in your Cloudflare dashboard.

Full (Strict) ensures a secure connection between both your visitors’ devices and Cloudflare and between Cloudflare and our servers.

From your site’s Cloudflare dashboard, click Crypto and then select Full (Strict) from the drop-down menu.

Connecting Your Domain

The first steps take place within your Cloudflare account, after which you will need to go to your registrar and add Cloudflare’s nameservers to the domain you are connecting. It is recommended that you locate you DNS records at your registrar or web host and have them handy before proceeding.

As soon as your Cloudflare account is created, you will be prompted to add a domain.

This has to be your actual domain (e.g. mydomain.com or mydomain.co.uk) and must not include any domain specific hostnames (e.g. www.mydomain.com or similar). Furthermore, the domain has to be an immediate child of an official top-level domain (or one of its official second-level domains). For example, mydomain.co.uk is permitted, mydomain.someisp.co.uk is not.

Enter your domain (not your temporary WPMU DEV domain) into the field provided and click Add Site.

Cloudflare add domain screen

You will be prompted to choose a plan. Do so and click Confirm Plan. If you choose a paid plan, a payment modal will appear. You will return to the setup process upon submitting your payment information.

Cloudflare will automatically locate your site’s DNS records.

Cloudflare DNS records

Compare the records found with those listed at your domain registrar or web host to verify that they match, and add any that are missing. If you skip this step your website might not resolve.

Also, click any orange clouds to turn them grey and then click Continue.

Change Your Nameservers

You will be prompted to change your nameservers at your registrar or web host. Cloudflare will provide two of its nameservers which should be cut and pasted to replace the existing records.

Cloudflare change nameservers

Once you have replaced your nameservers with those provided by Cloudflare, click Done! Check My Nameserver. Cloudflare will test the connection. If everything works, a success message will notify you that Cloudflare will begin caching your site’s content and serving it to visitors worldwide.

3.4.2 GoDaddy

Link to chapter 4

Login to GoDaddy, and click Manage Domains.

GoDaddy manage DNS

Once you log in, click on the ellipsis beside your owned domain and choose “Manage DNS”.

GoDaddy manage DNS

This will lead you to the Records of your chosen Domain.

GoDaddy DNS records list

Click on the “edit” icon beside the A-type and in the Points to* field enter the A Record value of your site (your IPV4 is located in your site’s Domains tab – in our example 104.248.40.26).

After that, edit the CNAME-type which has the www Name and in the Points to* field enter @.

Lastly, add one AAAA record. If you do not see an existing AAAA record, click the Add button and select AAAA from the menu of record types. In the Host field enter @ and in the Points to* field enter your AAAA record value (in our example 2a03:b0c0:3:e0::98:4001).

Got all this done? Excellent, the only thing left is to Set a new primary domain for your site.

3.4.3 Freenom

Link to chapter 4

Go to https://www.freenom.com, sign in to your account and then click on Services/My Domains:

Find your desired registered domain and click on the “Manage domain” button:

In the Domain module click on “Manage Freenom DNS”:

Which will lead you to a new window where you can set up your records.

You should add 3 new records, one for A record (your IPV4 is located in your site’s Domains tab – in our example 104.248.40.26), one for CNAME with www in the Name field (in this example devman-fn.cf) and one for AAAA record (in our example 2a03:b0c0:3:e0::98:4001) while keeping TTL Low (300):

Got all this done? Excellent, the only thing left is to Set a new primary domain for your site.

3.4.4 Namecheap

Link to chapter 4

Go to https://www.namecheap.com, login to your account and click on the Manage button beside your desired domain:

In the new window, navigate to the Advanced DNS tab.

Add one A record with @ in the Host field (your IPV4 is located in your site’s Domains tab, in our example 104.248.40.26), one CNAME record with www in the Host field (in this example devmantest.com) and one AAAA record with @ in the Host field (in our example 2a03:b0c0:3:e0::98:4001) while keeping TTL Low (5 mins):

Got all this done? Excellent, the only thing left is to Set a new primary domain for your site.

3.4.5 Google Domains

Link to chapter 4

Go to https://domains.google.com/registrar, log in to your account and click on the Configure DNS button:

Navigate down to Custom resource records and add one A record with @ in the Name field while adding your IP in the IP field (your IPV4 is located in your site’s Domains tab, in our example 104.248.40.26), one CNAME record with www in the Name field and @ in the Domain name field, and one AAAA Record with IPV6 in the IPV6 field (in our example 2a03:b0c0:3:e0::98:4001) while keeping TTL Low (10 mins):

Godaddy custom records

Got all this done? Excellent, the only thing left is to Set a new primary domain for your site.

3.4.6 Siteground

Link to chapter 4

Go to https://www.siteground.com/, log in to your account and navigate to “My Accounts” tab:

Press on the Go to cPanel button and in the follow-up window on the Advanced DNS Zone Editor:

Here you want to edit your domain’s A Record (your IPV4 is located in your site’s Domains tab, in our example we added 104.248.40.26), CNAME record with www (in our example we added devman-sg.com) and add a new AAAA record with your apex domain name as presented below (IPV6 in our example is 2a03:b0c0:3:e0::98:4001). Leave all other data intact.

Got all this done? Excellent, the only thing left is to Set a new primary domain for your site.

3.4.7 Porkbun

Link to chapter 4

Go to https://porkbun.com, log in to your account, click on Details (under your desired domain) and then on the Edit button beside DNS RECORDS:

In the new window create one A record with a blank Host field and enter your IPV4 in the Answer field (your IPV4 is located in your site’s Domains tab, in our example we used 104.248.40.26), one CNAME record with www in the Host field and enter @ in the Answer field (in our example this will resolve to devman-pb.com once saved) and one AAAA record with a blank Host field while adding your IPV6 in the Answer field (IPV6 in our example is 2a03:b0c0:3:e0::98:4001). Once saved you will get something like:

Got all this done? Excellent, the only thing left is to Set a new primary domain for your site.

3.4.8 Hover

Link to chapter 4

Go to https://www.hover.com/, log in to your account and click on “DNS” tab of your chosen domain.

Once there, edit your A record first. Leave @ as Hostname and enter your IP as your Target name (your IPV4 is located in your site’s Domains tab, in our example we used 104.248.40.26). Next, you want to edit your CNAME with www in its Hostname. Enter your apex domain name as your Target name (in our example we used devman-hv.com). Lastly, add one AAAA record, set @ as Hostname and enter your IPV6 as your Target name (in our example 2a03:b0c0:3:e0::98:4001). The end result should look something like this:

Got all this done? Excellent, the only thing left is to Set a new primary domain for your site.

3.4.9 Dreamhost

Link to chapter 4

Go to https://www.dreamhost.com/, log in to your account and then click on Domains/Manage domains:

In order to add your own DNS records, you need to “unpark” your domain by selecting “Deactivate parked” link and confirming the change.

Once done, select DNS, under your domain name, and add a new record as A Record with a blank Name field while using your IP in the Value field (your IPV4 is located in your site’s Domains tab, in our example 104.248.40.26). After that, add a new record as CNAME with www in the Name field while using your apex domain name in the Value field (in our example devman-dh.club). Lastly, add another record as AAAA Record with a blank Name field while using your IPV6 in the Value field (in our example 2a03:b0c0:3:e0::98:4001). The end result should look something like this:

Got all this done? Excellent, the only thing left is to Set a new primary domain for your site.

3.4.10 iPage

Link to chapter 4

Go to https://www.ipage.com/controlpanel, login to your account and then select Domain central.

Once in, click on your domain and select DNS. If DNS is not present here make sure you validated your domain and contact iPage support to get this added:

In the Modify section select A Record and edit the field that has your domain name in it (in this example devman-ip.space) with your WPMU DEV IP in the Points to field (your IPV4 is located in your site’s Domains tab, in our example 104.248.40.26). Once done, press on Add.

After adding your A Record, navigate to Modify section again and select CNAME. In the Host field add www and in the Points to field add your apex domain name (in our example devman-ip.space). Once sorted, press on Add.

Got all this done? Excellent, the only thing left is to Set a new primary domain for your site.

3.4.11 Bluehost

Link to chapter 4

Go to https://my.bluehost.com/cgi/dm/zoneedit, login to your account and then select your desired domain.

Once selected you will either need to add new records (if this is a new domain) or edit existing ones (if you already used this domain previously for another hosting service).

Add a new record as A type, enter @ in the Host Record and your WPMU DEV IP in the Points to field (your IPV4 is located in your site’s Domains tab, in our example 104.248.40.26). After that, add a new record as CNAME type with www in the Host Record and enter your domain name in the Points to field (in our example we used devman-bh.org). Lastly, add another record as AAAA type, enter @ in the Host Record and your WPMU DEV IPV6 in the Points to field (in our example 2a03:b0c0:3:e0::98:4001). The end result should look something like this:

Got all this done? Excellent, the only thing left is to Set a new primary domain for your site.

3.4.12 eNom

Link to chapter 4

Go to https://www.enom.com/, login to your account, navigate to Domain manager section and click on Registered domains:

Select your desired domain and in the Manage domain dropdown choose Host records. Once selected you will either need to add new records (if this is a new domain) or edit existing ones (if you already used this domain previously for another hosting service).

Add in the Address field for the CNAME Record type that has WWW as Host Name. Change the already present Record Type that has Host Name as @ from CNAME to A (Address) and enter your IPV4 in the Address field (in this example 46.101.107.111). Lastly, add another Record Type as AAAA (Address), enter @ in the Host name field and enter your IPV6 in the Address field (in this example 2a03:b0c0:3:d0::db3:7001). The end result should look something like this:

eNom edit DNS records

Finally, you need to choose your nameservers. Open the Manage Domain drop-down menu again, and click DNS Server Settings.

Most users can simply select the Our Servers radio button to use enom’s default nameservers. If you are using custom nameservers, select Custom and enter the server’s address into the fields provided.

When ready, click Save to preserve the configuration, and return to the Hosting control panel in The Hub to set your new primary domain. See the Set a new primary domain section below if you need help doing so.

3.5 Domains Support

Link to chapter 5

Need assistance adding or configuring domains? WPMU DEV members have access to 24/7 live support.