Help4 Net

Set up Help4 Net Pro

Pro is $8/month: one assigned domain or hostname plus its www companion, DET01 A-record ingress, managed proxy/WAF, and every eligible POP for CDN assets. Enterprise is $20/month and adds state/country GeoDNS. Existing Pro subscriptions keep their recurring price when grandfathered into Enterprise; Free accounts stay Free.

Keep nameservers and mail delivery unchanged. Save the current website records for rollback. Preserve MX, SPF, DKIM, DMARC, CAA, verification TXT, and mail-host records while changing only the qualified website A records.

Keep your DNS provider

Pro does not require changing nameservers. A fixed A record sends the initial website connection to DET01; it does not geographically select another POP. The plugin can use the full eligible asset network. Choose Enterprise for regional full-site DNS routing.

1. Attach the right production domain

  1. Sign in to the Help4 CDN client area.
  2. 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.
  3. Save the original hosting-server address in Hosting Origin IP. It must not be DET01 or another CDN POP address. The WordPress plugin reads the authenticated CDN profile and can retain an explicit hosting-origin override.
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. Qualify HTTPS, then change only website records

Complete hostname ownership, origin HTTPS, frontend certificate and forced-DET01 checks first. Keep the previous record values for rollback. Point the assigned hostname and its www companion to DET01:

example.com.      A    45.19.204.1
www.example.com.  A    45.19.204.1

For an assigned subdomain, use that hostname and its exact www companion. Remove conflicting website AAAA records unless Help4 has qualified the IPv6 route. Do not alter email, verification, or other service records.

Before cutoverRetain existing A/AAAA records and confirm both hostnames pass forced HTTPS tests.
After cutoverVerify public A/AAAA answers, TLS, served POP and uncached login/form paths.

3. Request a needed DNS entry safely

Pro keeps customer DNS at your existing provider. The Help4 DNS records editor and geographic full-site routing are Enterprise controls. Internal CDN asset DNS remains managed on all tiers.

  1. Collect the exact record owner, type, value, and requested TTL from the provider that needs the record.
  2. State whether it is for web, email, verification, or another service. Include the Pro service ID and assigned domain.
  3. Open a support ticket from the account that owns the Pro service. Paste the record values as text, not as a screenshot.
  4. 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.

4. Sync WordPress and refresh changed pages

  1. Install or update the Help4 CDN WordPress plugin.
  2. Open Help4 CDN in WordPress and save the configured settings once to sync the assigned domain and service profile.
  3. 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