Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Hosting · Info

WP Engine DNS Settings Explained: What Each Option Does

WP Engine DNS Settings Explained: What Each Option Does

Short answer

WP Engine shows the DNS values for each site on the Domains page of its User Portal. Most sites use A records for the root domain and a CNAME for www, entered at your DNS provider. Leave email records untouched, then add SSL once DNS points to WP Engine.

Key takeaways

  • Copy DNS values from the Domains page in the WP Engine User Portal.
  • The root domain usually needs A records; www uses a CNAME.
  • Do not change MX or email TXT records when switching hosts.
  • Domain Connect can apply records automatically at supported registrars.
  • Lower the TTL before the switch for faster changes.
  • Add the free SSL certificate after DNS points to WP Engine.

What DNS settings does WP Engine need?

WP Engine needs your domain's DNS to point at its network, usually with a CNAME record for www and A records for the root domain, using the exact values shown for your site in the WP Engine User Portal.

DNS tells browsers which server hosts your site. When you move a site to WP Engine, you change a few DNS records so visitors reach WP Engine instead of your old host.

The records live wherever your DNS is managed. That is often your domain registrar, Cloudflare, or your old host. WP Engine gives you the values, and you enter them at your DNS provider.

WP Engine's guide to pointing DNS to WP Engine is the official reference. This article explains what each setting means so the portal values make sense.

Where do you find your WP Engine DNS values?

Log in to the WP Engine User Portal, open your site's environment, go to the Domains page, add your domain, and the portal shows the DNS records to create.

  1. Log in to the WP Engine User Portal.
  2. Select the site and the environment, usually production.
  3. Open Domains.
  4. Add your domain, both the root and the www version.
  5. Open the DNS details shown for each domain.

The values depend on your network type and plan. Always copy them from the portal rather than from an old guide or another site. Values can differ between accounts.

Before you change DNS, make sure the site is migrated and working on WP Engine's temporary address. Our guide on migrating a site to WP Engine covers that step.

What does each DNS record do?

A records point a domain to an IP address, CNAME records point a name to another name, and TXT or MX records handle verification and email, which WP Engine does not manage.

RecordTypical use with WP EngineExample host
APoints the root domain to WP Engine IP addresses@ or the bare domain
CNAMEPoints www to a WP Engine hostnamewww
TXTDomain verification, SPF for email@
MXRoutes email to your mail provider@

Only the A and CNAME records change for the website. Leave MX and email-related TXT records alone, or your email will stop working.

For a general overview of these record types, see our guide on WordPress DNS settings.

Why does the root domain use A records?

DNS standards do not allow a normal CNAME on the root domain, so the root usually gets A records pointing to WP Engine's IP addresses, while www can use a CNAME.

The root domain, also called the apex, holds other records such as MX and the start of authority. A CNAME there would conflict with them.

That is why WP Engine typically gives you:

  • A records for the root domain.
  • A CNAME for www.

Some DNS providers offer CNAME flattening, which lets you use a CNAME-style record at the root. Cloudflare explains how this works in its CNAME flattening guide. If your provider supports it, WP Engine may suggest a CNAME for both.

What is the difference between Advanced Network and legacy settings?

WP Engine's newer network options use shared hostnames and IP addresses tied to its edge network, while older legacy setups pointed to a site-specific address, so the values you need depend on how your site is configured.

WP Engine has offered different network options over time, including its Advanced Network and Global Edge Security. These route traffic through an edge network for caching and protection.

What this means for you:

  • The portal shows the right values for your site's network.
  • Older guides may list values that no longer apply.
  • Switching network type later can require new DNS records.

If you are not sure which network your site uses, the Domains page in the portal shows it. Our guide on whether WP Engine uses a CDN explains the edge network side.

Can WP Engine set up DNS for you automatically?

For some registrars, WP Engine supports Domain Connect, which lets you approve the DNS changes in a pop-up instead of typing records by hand.

WP Engine's Domain Connect guide lists how it works. When your provider supports it, the portal offers a button to apply the records.

You sign in to your DNS provider, review the changes and approve them. The records are created for you.

Check the result afterwards. Make sure the existing email records were not changed and that both the root and www domains point to WP Engine.

Should you lower the TTL before switching?

Yes; lowering the TTL on your existing records a day or two before the switch makes the change take effect faster and makes rolling back quicker if something goes wrong.

TTL, or time to live, tells other DNS servers how long to cache a record. A long TTL means old values stay cached for hours.

A simple plan:

  1. A day or more before the move, lower the TTL on your A and CNAME records to a short value, such as five minutes.
  2. Make the switch to WP Engine's values.
  3. Once everything works, raise the TTL again.

Even with a short TTL, some networks cache longer. Our guide on how long DNS propagation takes explains why.

How do you check that DNS is pointing to WP Engine?

Use a DNS lookup tool to check that your root and www records show the values from the portal, then confirm the Domains page in WP Engine shows the domain as pointed.

A tool such as whatsmydns.net shows what DNS servers around the world return for your domain. Check A records for the root and CNAME records for www.

Signs that the switch has worked:

  • Lookup tools show WP Engine's values in most locations.
  • The WP Engine portal marks the domain as pointed or active.
  • Your site loads with WP Engine's response headers.

If some locations still show old values, wait. Propagation can take a few hours.

How does SSL work after pointing DNS?

Once DNS points to WP Engine, you can add a free Let's Encrypt certificate in the portal's SSL section, and WP Engine renews it automatically.

The certificate can only be issued after DNS reaches WP Engine, because the certificate authority checks that the domain points there. Let's Encrypt explains how that domain check works.

Add the certificate for both the root and www versions. Then set your preferred version as the primary domain and redirect the other one to it.

If you see SSL errors right after switching, give propagation a little time. Our guide on fixing ERR_SSL_PROTOCOL_ERROR helps if errors continue.

What about Cloudflare in front of WP Engine?

You can use Cloudflare for DNS with WP Engine, but proxying traffic through your own Cloudflare account on top of WP Engine's edge network needs care to avoid SSL and caching conflicts.

If Cloudflare only hosts your DNS, set the records to DNS only, the gray cloud, and enter WP Engine's values. That is the simplest setup.

If you want Cloudflare's proxy as well, follow WP Engine's guidance for your network type. Cloudflare also documents a WP Engine provider setup for accounts using its SaaS features.

What DNS problems are common with WP Engine?

The usual problems are wrong or old values, records left pointing to the old host, deleted email records, a missing www record, and SSL that was added before DNS finished propagating.

Quick fixes:

  • Site still on old host. Check for duplicate A records and remove the old ones.
  • Email stopped working. Restore the MX and email TXT records from your old DNS.
  • www does not load. Add the CNAME for www from the portal.
  • Site not found errors. See our guide on fixing DNS_PROBE_FINISHED_NXDOMAIN.

If the records match the portal and the site still fails after a day, contact WP Engine support with your domain name and a screenshot of your DNS records.

Frequently asked questions

Where do I find my WP Engine IP address?

Log in to the WP Engine User Portal, open your site's environment and go to Domains. After adding your domain, the portal shows the DNS records to use, including any IP addresses for the root domain. Values differ by network type, so copy them from your own portal.

Does WP Engine host my DNS?

Usually not. Most people keep DNS at their registrar or a service like Cloudflare and point records to WP Engine. You add the values WP Engine provides at whichever DNS provider manages your domain.

Will changing DNS to WP Engine break my email?

Not if you only change the website records. Email depends on MX and related TXT records, which should stay as they are. Problems happen when people delete all records or move DNS providers without copying the email records.

How long does it take for WP Engine DNS changes to work?

Often minutes to a few hours, depending on the TTL of your old records and how long networks cache them. Lowering the TTL before switching speeds things up. A full day is a safe window before assuming something is wrong.

Can I use Cloudflare DNS with WP Engine?

Yes. The simplest setup uses Cloudflare for DNS only, with the gray cloud, and WP Engine's record values. Using Cloudflare's proxy as well is possible but needs extra care, so follow WP Engine's guidance for your network type.

Sources

  1. Point DNS for Your Domain Name to WP Engine WP Engine
  2. Domain Connect WP Engine
  3. CNAME flattening Cloudflare
  4. WP Engine provider guide Cloudflare
  5. Let's Encrypt Let's Encrypt

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.