You love your shiny new WordPress.com 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 WordPress.com or another domain registrar. To map a domain you already own, simply follow these instructions. Domain mappings are included for free on WordPress.com 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.
Managing DNS Records
If you map a 2nd-level domain (e.g. example.com), you can easily add a subdomain (e.g. vip.example.com) 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
Mapping to WordPress.com
If your site will live on a 2nd-level domain (example
.com), 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 WordPress.com, the following steps should be taken to set up the domain least a week before the launch:
- Send us the ZONE file for your domain including any subdomains or MX records for email.
- We will set up the domain mapping on the WordPress.com site
- 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).
- Once setup is complete, you can verify and switch to our nameservers.
- When your site is ready to launch, we will update your website’s entry to point to your new WordPress.com 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 WordPress.com Nameservers
The nameservers to use are:
We provide a handy DNS management tool for you to create A, MX, CNAME, and TXT records.
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.
If your site will live on a subdomain (
sub.example.com, all that is required is a CNAME. When the site is ready to launch, you can create a CNAME entry pointing to your registered WordPress.com site:
sub.example.com IN CNAME subexample.wordpress.com.
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.
Every WordPress.com 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 WordPress.com Dashboard; just head to Settings > Domains and select the domain you would like to be primary.
WordPress.com 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.
WordPress.com does not support hosting the root of a site in the subdirectory of a site’s primary domain.
WordPress.com DNS does not currently support DNSSEC. If managing your DNS on WordPress.com you’ll need to disable DNSSEC at your registrar.