Use this order for a Pro production domain: attach the domain to the active service, preserve the DNS zone, move nameservers when the Help4 zone is ready, sync WordPress, then verify the website, mail, and cache path.
Do not treat a web cutover as a mail migration. Before you change nameservers, save the current MX, SPF, DKIM, DMARC, CAA, verification TXT, and mail-host records. Do not replace or delete those records while working on web delivery.
Watch the Pro setup walkthrough
A short, captioned visual walkthrough of the safe order for DNS, WordPress sync, and cache verification.
Captions are included. The video is a visual guide; use the numbered instructions below for exact record values and verification commands.
Open the active Pro service and enter one production base domain, such as example.com. Do not enter https://, a path, or a staging hostname.
Wait for the service to show the assigned domain and DNS readiness state. If it remains waiting for DNS, finish the nameserver onboarding before expecting full proxy coverage.
Pro is bound to one production domain. Open a support ticket before moving that service to a different domain so entitlement, origin, DNS, and TLS validation remain aligned.
2. Move DNS only after the zone is ready
Use the DNS cutover tutorial for the exact registrar workflow and all six Help4 nameservers. Confirm the zone includes website, mail, verification, and special-subdomain records before saving a delegation change.
Before delegationExport the existing DNS zone and confirm the active origin and certificate are ready for the assigned domain.
After delegationCheck authoritative nameservers first, then load public web pages and send and receive a real mail test.
3. Request a needed DNS entry safely
The current Pro client area shows the assigned domain, DNS readiness, and site-scoped API details. The self-service DNS records editor and independent proxy/WAF mode switches are Enterprise controls. Do not create a second zone or edit Help4-managed routing records to work around that boundary.
Collect the exact record owner, type, value, and requested TTL from the provider that needs the record.
State whether it is for web, email, verification, or another service. Include the Pro service ID and assigned domain.
Open a support ticket from the account that owns the Pro service. Paste the record values as text, not as a screenshot.
After confirmation, verify the record and test the service it enables. Keep the pre-change zone export until testing is complete.
Good requestProvider-supplied TXT or CNAME verification record, exact owner and value, and the affected service identified.
Stop and askAny request to alter an apex web record, MX record, SPF, DKIM, DMARC, DNSSEC setting, or existing Help4-managed record.
Need client-area record editing, GeoDNS record routing, or independent delivery and WAF modes? Use the Enterprise controls tutorial before changing plan or traffic settings.
Open Help4 CDN in WordPress and save the configured settings once to sync the assigned domain and service profile.
After a content, image, plugin, or theme change, refresh the smallest affected path set first. Use the JSON cache refresh guide for an authenticated integration.
Use site-scoped credentials only from approved server-side automation or the plugin settings. Never include an API secret in a browser script, screenshot, email, or support ticket.
5. Verify the live result
Confirm delegation: dig +short NS example.com.
Open the home page, a deeper page, a form or login path, and a current image in a private browser session.
Send and receive a test email after a nameserver change.
Use curl -I https://example.com/ to inspect the current response without exposing secrets.