InstaWP Docs

Appearance

Map a root domain when your registrar doesn't allow a CNAME ​

To map a custom domain, InstaWP asks you to point it with a CNAME record — for example, point www.example.com at your InstaWP hostname (your-site.instawp.site). That works perfectly for subdomains like www, blog, or shop.

The problem starts at the root domain (also called the apex or naked domain) — the bare example.com with no subdomain in front. Many registrars will not let you add a CNAME record on the root, and this is not a bug on their side — it's how the DNS standard works. A root domain must already hold NS and SOA records, and the DNS spec (RFC 1034) forbids a CNAME from co-existing with any other record on the same name. So the registrar simply blocks it.

This guide explains why you can't just "use an A record instead," and walks through the three supported ways to point a root domain at your InstaWP site.

In this documentation, we will cover:

Before you start — check the plan. Mapping a custom domain requires the Starter plan or higher. Sites on the Sandbox plan can't be mapped to a custom domain, because Sandbox doesn't include the CDN or Shield needed for a live, public-facing site. Upgrade the site's plan first if needed.

Why you can't just use an A record ​

The obvious workaround for a blocked CNAME is to add an A record (which points a name to a numeric IP address) at the root instead. With InstaWP, this does not work, and it's important to understand why before you try it.

InstaWP serves your site through a CDN with dynamic IP addresses. The IP your domain would need to point to is not fixed — it can change at any time as traffic is routed for performance and protection. If you hard-code a single IP into an A record, that IP can go stale, and your site will start returning errors or the wrong content with no warning.

That's why InstaWP hands you a hostname (your-site.instawp.site) rather than an IP — the hostname always resolves to the correct current address. The methods below are all ways to point your root domain at that hostname, without needing a fixed IP and without a plain root CNAME.

Which method should I use? ​

MethodUse it whenTrade-offs
ALIAS / ANAME recordYour DNS provider offers an ALIAS or ANAME record type (e.g. DNSimple, DNS Made Easy, ClouDNS, easyDNS — check your provider's docs).The cleanest option — the root resolves natively to InstaWP. Only works if your provider supports the record type.
Cloudflare CNAME flatteningYour provider does not support ALIAS/ANAME, but you're willing to move your DNS (nameservers) to Cloudflare's free plan.Works with any registrar. Requires a free Cloudflare account and a one-time nameserver switch.
Domain forwardingYou'd rather not move your DNS at all, and you're fine with visitors landing on the www version of your site.Simplest to set up. The root domain redirects to www.example.com instead of serving the site directly.

If your registrar supports it, Method 1 (ALIAS/ANAME) is the best choice. If not, choose Method 2 for a true root-domain mapping, or Method 3 if you just want it working quickly and don't mind the www redirect.

An ALIAS (sometimes called ANAME) record behaves like a CNAME, but it's allowed on the root domain. Your DNS provider resolves the target hostname behind the scenes and answers with the right address — so your root domain always points to the correct InstaWP CDN address even though the underlying IPs change.

Step 1 — Copy your InstaWP hostname from the Map Domain modal ​

In your InstaWP dashboard, open the Sites page, click the horizontal ellipsis (⋯) next to your site, and choose Map Domain. Click the Map Domain button, enter your root domain (example.com), and choose whether it should be Primary or Alias. InstaWP will show you the hostname to point at — copy it.

The Map Domain modal in the InstaWP dashboard, showing the CNAME target hostname to copy

The Primary domain is your site's main address; an Alias domain is an additional domain that redirects to the primary one.

Keep this modal open — you'll come back to click Map Domain once the DNS record is in place.

Step 2 — Add the ALIAS/ANAME record at your DNS provider ​

Go to your DNS provider's DNS management panel and choose to add a new record.

Adding a new record in the DNS management panel of your provider

Select ALIAS or ANAME as the record type, enter @ (which represents the root domain) in the Name / Host field, and paste your InstaWP hostname (e.g. your-site.instawp.site) into the Target / Value field.

Selecting ALIAS/ANAME as the record type, with @ as the host and the InstaWP hostname as the target

Step 3 — Save the record ​

Save the record. It should now appear in your provider's record list.

The saved ALIAS/ANAME record in the DNS records list

Tip — also map www. Add a normal CNAME record for www pointing to the same InstaWP hostname, so both example.com and www.example.com reach your site. www is a subdomain, so a CNAME is always allowed there.

Step 4 — Complete the mapping in InstaWP ​

Return to the Map Domain modal in your InstaWP dashboard and click the Map Domain button to finish. Because the ALIAS/ANAME record resolves the hostname dynamically, both your root domain and subdomains stay pointed at the correct InstaWP site even behind the CDN's dynamic IPs. Then jump to Verify the mapping and issue SSL.

Method 2 — Cloudflare DNS with CNAME flattening (works everywhere) ​

If your registrar doesn't offer an ALIAS/ANAME record, you can move your domain's DNS to Cloudflare's free plan. Cloudflare supports CNAME flattening: you add a CNAME on the root domain, and Cloudflare automatically resolves it and serves it as an A record — so the root domain maps to InstaWP correctly, with no fixed IP required. Your domain stays registered with your current registrar; only the nameservers change.

Step 1 — Add your domain to Cloudflare and switch nameservers ​

Create a free Cloudflare account and add your domain. Cloudflare will give you two nameservers — update your domain's nameservers at your registrar to those values. Cloudflare's own guide walks through this: Add a site to Cloudflare. Nameserver changes can take a little time to activate; Cloudflare emails you when your domain is active.

Step 2 — Copy your InstaWP hostname from the Map Domain modal ​

In InstaWP, open the site's Map Domain page (Sites → ⋯ → Map Domain), click Map Domain, enter your root domain, choose Primary or Alias, and copy the hostname InstaWP provides.

The InstaWP Map Domain modal showing the hostname to copy

Step 3 — Add the CNAME record in Cloudflare ​

In the Cloudflare dashboard, go to DNS → Records and click Add record.

Adding a DNS record in the Cloudflare DNS Records page

Create a CNAME record with @ as the Name (Cloudflare flattens this at the root) and your InstaWP hostname as the Target. Repeat with www as the Name and the same hostname as the Target, so both versions of your domain resolve. Save the record.

Adding the CNAME record in Cloudflare with @ / www as the name and the InstaWP hostname as the target

The record then appears in your Cloudflare records list.

The CNAME record shown in the Cloudflare records list

Proxy status. When you first map the domain, it's usually easiest to set the record's proxy status to DNS only (grey cloud) so InstaWP can validate the domain and issue SSL. Once the site is mapped and the SSL certificate is active, you can turn the orange‑cloud Proxy back on for Cloudflare's CDN and security features if you want them.

Step 4 — Complete the mapping in InstaWP ​

Back in the Map Domain modal, click Map Domain to finish, then continue to Verify the mapping and issue SSL.

Method 3 — Domain forwarding to the www subdomain ​

If you'd rather not move your DNS to Cloudflare and your provider has no ALIAS/ANAME option, you can map your site to the www subdomain (where a CNAME is always allowed) and then use your registrar's domain forwarding feature to redirect the bare root domain to www. Visitors who type example.com are redirected to www.example.com, where your InstaWP site lives.

This is the quickest path and needs no third‑party account, with one trade‑off: the root domain redirects to www rather than serving the site directly.

The full walkthrough (with a Namecheap example) is covered in its own guide: Using domain forwarding as an alternative to CNAME.

In short:

  1. Map your site to www.example.com — add a normal CNAME for www pointing to your InstaWP hostname, and complete the mapping in the InstaWP dashboard.
  2. Set up a redirect on the root domain — in your registrar's domain forwarding / redirect settings, forward example.com to https://www.example.com using a Permanent (301) redirect (a 301 correctly passes SEO signals to the www version).
  3. Save and wait for the change to propagate.

Most registrars (GoDaddy, Namecheap, Porkbun, and others) offer this under a name like "Domain forwarding," "Redirect Domain," or "URL redirect" — the concept is the same everywhere.

Verify the mapping and issue SSL ​

Whichever method you used, confirm the mapping resolved and that SSL is active:

  1. Wait for propagation. DNS and nameserver changes can take anywhere from a few minutes to 24–48 hours to fully propagate, though it's often much faster.
  2. Check that the domain resolves. Visit your domain in a browser. Once DNS points to InstaWP, your site should load on the custom domain.
  3. Confirm SSL. InstaWP automatically issues a free Let's Encrypt SSL certificate once your domain's DNS resolves to InstaWP — so the padlock (HTTPS) appears on its own. If it hasn't issued after DNS has propagated, open the site's Connectivity → Map Domain page and click Retry SSL next to the mapped domain to re‑trigger issuance.

Troubleshooting ​

  • The root domain still doesn't resolve. DNS changes take time — give propagation up to 24–48 hours. You can check what your domain currently resolves to with a public DNS lookup tool.
  • SSL isn't issuing. SSL can only be issued after the domain's DNS resolves to InstaWP. Confirm the record is correct and has propagated, then use Retry SSL on the Connectivity → Map Domain page. If you used Cloudflare with the proxy on, switch the record to DNS only temporarily so InstaWP can validate the domain and issue the certificate.
  • You're on the Sandbox plan. Custom domain mapping requires Starter or higher — upgrade the site's plan first.
  • You added an A record and the site broke later. Remove it — InstaWP's CDN uses dynamic IPs, so a hard-coded A record on the root will eventually go stale. Use one of the three methods above instead.

Docs are open — edit on GitHub. Built with VitePress.

© InstaWP