Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.
Pointing DNS is the last step of moving a site to WP Engine, and the one most likely to cause a nervous hour. It is not hard. You add the domain in the portal, change two records at your DNS host, and wait. Here is the exact order I use.
Before you touch DNS
- Make sure the site is fully migrated and working on its temporary WP Engine URL. The migration plugin guide covers that part.
- If you bought Global Edge Security, enable it first. It changes which DNS values you use.
- Lower the TTL on your current records to 300 seconds a day ahead if your DNS host allows it. Changes then spread faster.
- Write down your current MX and TXT records. You will not change them, but you want a copy.
Step 1: Add the domain in the User Portal
- Go to Sites and select the production environment.
- Open Domains (under Manage if the menu is collapsed).
- Click Add domain, enter the root domain, and choose Add and set up domain.
- Verify ownership when asked.
- Pick automatic setup (handled by Entri for supported DNS providers) or manual setup.
Your exact CNAME target and IP addresses are under View DNS Details in the three-dot menu next to the domain. Use those values, not ones from a blog post.
Step 2: Set the DNS records
| Record | Name | Points to | Notes |
|---|---|---|---|
| CNAME (flattened) | @ or example.com | Your WP Engine CNAME | Preferred for the root if your DNS host supports CNAME flattening |
| A (two records) | @ | The two WP Engine IPs | Use this if flattening is not available. Add both IPs. |
| CNAME | www | example.com | If www already points at the root, leave it |
| CNAME | blog, shop, etc. | Your WP Engine CNAME | For any subdomain on the same site |
Delete the old A record for the root before you add the new one. Also delete any AAAA (IPv6) records on the root unless you use Cloudflare, because WP Engine does not serve over IPv6 and a stale AAAA record sends some visitors to the old host.
If your registrar only lets you change nameservers, move DNS to Cloudflare and use its CNAME flattening. My WP Engine and Cloudflare post explains how the two fit together.
Step 3: Wait, then check
- Most changes show up within minutes. The official ceiling is 48 hours.
- Automatic setup through Entri uses a one-hour TTL, so it usually settles in about an hour.
- Use Refresh Status on the Domains page, or check from several locations at WhatsMyDNS.net.
SSL
Once DNS points at WP Engine’s network, SSL and HTTPS are turned on for you. A red certificate warning in the first few minutes is normal while things propagate. If you need a third-party certificate instead, add it on the SSL page in the portal.
Things that go wrong
- Email stops working: automatic setup can remove records it sees as conflicting. Review the change list before you approve it and compare it to your saved MX and TXT records.
- Half your visitors see the old site: an old A or AAAA record is still there. Remove it.
- Mixed content warnings: the database still has http:// links. Run a search and replace for the old URL.
- Cached old pages: clear the WP Engine cache after the switch.
Moving to WP Engine? Free SSL, a global CDN, and automatic domain setup for supported DNS providers are included on every plan.
FAQ
Should I use a CNAME or an A record for WP Engine?
WP Engine recommends a flattened CNAME for the root domain. If your DNS host cannot flatten CNAMEs, use two A records pointing to both WP Engine IP addresses.
How long does DNS take to point to WP Engine?
Usually minutes, sometimes up to 48 hours. Automatic setup through Entri uses a one-hour TTL, so it often finishes in about an hour.
Does WP Engine give me a free SSL certificate?
Yes. Once DNS points to WP Engine, SSL and HTTPS are enabled automatically. You can also upload a third-party certificate on the SSL page.