Mapping Your Domain and Managing DNS VIP platform specific

This document is for sites running on VIP.

Learn more

Overview #

You love your shiny new site and you probably want to put your own domain on it.

To proceed forward, you’ll need to have first registered your domain with a domain registrar. If you haven’t yet, you can register your domain through or another domain registrar. To map a domain you already own, simply follow these instructions. Domain mappings are included for free on VIP.

Since DNS propagation can take up to 72 hours, you will want to begin this process at least a week before your planned launch date.

↑ Top ↑

Managing DNS Records #

Once you point your domain to WordPress nameservers, you can continue to manage your domain with our Domain Management tools which allow you to add custom DNS records.

If you map a 2nd-level domain (e.g., you can easily add a subdomain (e.g. to it.

There are a few kinds of DNS changes that you cannot make directly through our tools, but that can be requested by contacting us via a ticket:

  • Adding wildcard DNS records
  • Adding TXT records that exceed 192 characters in length
  • Changing TTL values for DNS records
  • Adding TXT records for subdomains
  • Managing NS records for a domain

↑ Top ↑

Mapping to #

If your site will live on a 2nd-level domain (, we highly recommend hosting it with our DNS servers. In order to smoothly handle any volume of traffic and weather any malicious attack, our load balancing and high availability solutions are dependent on us being the name server for 2nd-level domains. By taking this approach, it enables our skilled systems team to effectively route traffic to additional servers, mitigate attacks, or accommodate for an outage in one of our data centers.

If you have an existing website that you are migrating to, the following steps should be taken to set up the domain least a week before the launch:

  1. Send us the ZONE file for your domain including any subdomains or MX records for email.
  2. We will set up the domain mapping on the site
  3. We will set up the DNS entries to mirror your current setup (so your existing site continues to work when you point your domain to our nameservers).
  4. Once setup is complete, you can verify and switch to our nameservers.
  5. When your site is ready to launch, we will update your website’s entry to point to your new site.

This provides the most fluid migration and means we’re around to pull the actual trigger and assist with any post-launch tasks.

Using Nameservers #

The nameservers to use are:

We provide a handy DNS management tool for you to create A, MX, CNAME, and TXT records.

↑ Top ↑

Using 3rd-party Nameservers #

If you’re required to host the DNS elsewhere, you can create A records pointing to two or more of our IPs. To get this information, please contact us using the contact form inside your Dashboard.

At least a couple of days before the migration you will want to change the TTL to 300, or if that is not allowed by your current DNS hosting, the lowest value allowed to allow for the smoothest transition possible.

↑ Top ↑

Subdomain ( #

If your site will live on a subdomain (, all that is required is a CNAME. When the site is ready to launch, you can create a CNAME entry pointing to your registered site: IN CNAME

Note that you will want to change the TTL for the subdomain to 300 or the next lowest value allowed to make the transition as smooth as possible.

↑ Top ↑

Primary Domains #

Every site can have multiple mapped domains but only one Primary Domain. This the canonical domain name for your site and all other domains registered against the site will redirect accordingly. The Primary Domain can be set from the Domains page in the Dashboard; just head to Settings > Domains and select the domain you would like to be primary.

↑ Top ↑

www subdomain # does not support using the www subdomain as a primary hostname for a site. The www subdomain is typically set up as a CNAME to the root domain, and requests to it are then redirected to the root domain.

↑ Top ↑

Subdirectories # does not support hosting the root of a site in the subdirectory of a site’s primary domain.

↑ Top ↑

DNSSEC # DNS does not currently support DNSSEC. If managing your DNS on you’ll need to disable DNSSEC at your registrar.

Ready to get started?

Drop us a note.

No matter where you are in the planning process, we’re happy to help, and we’re actual humans here on the other side of the form. 👋 We’re here to discuss your challenges and plans, evaluate your existing resources or a potential partner, or even make some initial recommendations. And, of course, we’re here to help any time you’re in the market for some robust WordPress awesomeness.