CloudFlare DNS Manager for WHMCS Print

CloudFlare DNS Manager connects WHMCS domains and services to Cloudflare DNS zones. Customers can manage records, eligible proxy settings, zone SSL/TLS modes and DNSSEC from the client area.

Requirements and installation

1. Use WHMCS 8.9 or later, a compatible PHP environment with cURL, a Cloudflare account and a valid module license. Use the PHP requirements of both WHMCS and your supplied module release.
2. Upload modules/addons/cloudflaredns_manager/ into the WHMCS root without renaming it.
3. Open WHMCS Addon Modules, activate CloudFlare DNS Manager and choose Configure.
4. Enter the license key, CloudFlare Email and Global API Key from Cloudflare's API credentials page. This module uses email plus Global API Key authentication, not a scoped API token.
5. Set the Default TTL, review Additional Protected Domains and assign administrator access. Save Changes.
6. Open the addon, synchronize or associate a test zone with the correct WHMCS domain or service, and verify customer access.

Module settings

Default TTL is 3600 seconds. Additional Protected Domains accepts a comma-separated list of domains hidden from customer management; the WHMCS installation domain is automatically protected.

Clear Data on Deactivation removes stored WHMCS zone data without deleting the actual Cloudflare zones. Leave it disabled during ordinary upgrades. SSL/TLS mode, DNSSEC and record proxy settings are managed per zone or record; they are not the global addon fields described in older instructions.

Domain lifecycle and nameservers

The registration and transfer hooks can create zones or associate existing zones. The addon does not require a separate provisioning server module for domain integration.

Update domain delegation at the registrar to the Cloudflare-assigned nameservers shown for that zone. Creating the zone does not by itself update the registrar. Use the nameserver check after changing delegation.

Deleting a WHMCS domain can delete its Cloudflare DNS zone. The domain-delete hook attempts provider deletion when the mapped zone has no service association. If it also has a service association, the hook removes only the domain association. A service termination clears the service association without deleting the provider zone. Export records and check associations before deleting domains.

Administrator and customer use

Administrators can create and delete zones, synchronize zones, associate them with domains or services, manage records and configure DNSSEC or SSL/TLS. Customers reach DNS Management through the Domains menu or the domain details Actions sidebar and can manage their associated zones.

Record types include A, AAAA, CNAME, MX, TXT, SRV, NS, CAA and TLSA. Add a record with its required name, value and TTL, then verify DNS resolution. Protected nameserver records cannot be changed through the customer editor.

Proxy and SSL/TLS settings

Eligible A, AAAA and CNAME records can use the orange-cloud proxy or grey-cloud DNS-only mode. DNS-only records resolve directly to the origin; proxy behavior depends on Cloudflare's supported protocols and account features. Keep mail-related hostnames DNS-only unless your provider explicitly supports the intended protocol.

• Off: Does not provide visitor-to-Cloudflare HTTPS encryption.
• Flexible: Encrypts the visitor-to-Cloudflare connection, but not Cloudflare-to-origin HTTP.
• Full: Encrypts both connections without the certificate validation required by Strict mode.
• Full (Strict): Requires an appropriate valid origin certificate. Configure and test the origin before switching.

Import, export and DNSSEC

Export the zone before a bulk change. The BIND importer offers Merge, Replace and Append. Merge skips records already present; Append can add duplicates. Replace removes existing records as part of the import, so review the file and keep an export before proceeding. Check the resulting zone after import.

1. Enable DNSSEC in the zone interface.
2. Copy the DS values provided by Cloudflare to the registrar.
3. Verify public DNSSEC validation after the change propagates.

Enabling DNSSEC at Cloudflare does not publish the DS record at your registrar. Coordinate DS removal or replacement before disabling DNSSEC or moving DNS providers to avoid validation failures.

Troubleshooting and updates

• If authentication fails, check the account email and Global API Key, PHP cURL and outbound HTTPS to the Cloudflare API.
• If a zone is missing, check synchronization, ownership associations, protected domains and the relevant registrar hook.
• If customer navigation is missing, verify the addon is active and the customer is logged in; custom themes may change sidebar placement.
• If nameservers do not match, check registrar delegation against the zone's assigned nameservers rather than copying nameservers from another account.

Back up the WHMCS database and module files before upgrading. Preserve associations and keep destructive deactivation disabled. Contact ArkHost support with module, WHMCS and PHP versions and redacted errors.