Skip to content

Commit b102a54

Browse files
authored
Add Zone Hold to WP Engine O2O Provider Guide
1 parent f7a87a4 commit b102a54

File tree

1 file changed

+8
-0
lines changed
  • src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides

1 file changed

+8
-0
lines changed

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/wpengine.mdx

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,14 @@ If you cannot activate your domain using [proxied DNS records](/dns/proxy-status
4444

4545
<Render file="provider-guide-compatibility" />
4646

47+
## Zone hold
48+
49+
Because you have your own Cloudflare zone, you have access to the zone hold feature, which is a toggle that prevents your domain name from being created as a zone in a different Cloudflare account. Additionally, if the zone hold feature is enabled, it prevents the activation of custom hostnames onboarded to WP Engine. WP Engine would receive the following error message for your custom hostname: `The hostname is associated with a held zone. Please contact the owner of this domain to have the hold removed.`
50+
51+
To successfully activate the custom hostname on WP Engine, the owner of the zone needs to [temporarily release the hold](/fundamentals/setup/account/account-security/zone-holds/#release-zone-holds). If you are only onboarding a subdomain as a custom hostname to WP Engine, only the subfeature titled `Also prevent Subdomains` needs to be temporarily disabled.
52+
53+
Once the zone hold is temporarily disabled, follow WP Engine's instructions to refresh the custom hostname and it should activate.
54+
4755
## Additional support
4856

4957
<Render file="provider-guide-help" params={{ one: "WP Engine" }} />

0 commit comments

Comments
 (0)