BunnyDNS Manager for WHMCS Print

BunnyDNS Manager is a WHMCS addon for managing Bunny.net DNS zones and records. It includes customer DNS management, domain lifecycle hooks, BIND import/export, nameserver checks and DNSSEC controls.

Requirements and installation

1. Use WHMCS 8.9 or later, a compatible PHP environment with cURL, a Bunny.net account with API access and a valid module license. Check the supplied release requirements against your WHMCS PHP requirements.
2. Extract the release into the WHMCS root, preserving modules/addons/bunnydns_manager/. Current releases load hooks.php from that addon directory; they do not require a separate includes/hooks/bunnydns_manager.php.
3. Activate BunnyDNS Manager in WHMCS Addon Modules.
4. Enter the license key and the Account API key from Bunny.net. The module sends that key in the AccessKey header.
5. Set administrator access, default TTL and the DNS resolver used for nameserver verification. Save the settings.
6. Review Auto-Create Zones and Auto-Delete Zones before testing with a domain you control.

Configuration

• Default TTL: The initial value is 3600 seconds. Record validation accepts TTL values from 120 to 86400.
• Additional Protected Domains: Enter comma-separated domains that must not be managed through the customer interface. The WHMCS installation domain is automatically protected.
• DNS Resolver for Nameserver Verification: Choose the Cloudflare, Google or Quad9 resolver listed in the settings.
• Auto-Create Zones: Controls creation or association during supported registration and transfer hooks.
• Auto-Delete Zones: Controls deletion of provider zones when a WHMCS domain is deleted. Review the warning below before relying on this setting.
• Clear Data on Deactivation: Removes stored WHMCS zone data on deactivation, not the DNS zones at Bunny.net. Leave it disabled during ordinary upgrades.

Nameservers and domain automation

Creating a zone is not the same as changing registrar delegation. Update the domain at its registrar to use the nameservers shown by the module, then run the nameserver check.

Custom nameservers are optional. Enable Custom Nameservers and enter Custom Nameserver 1 and 2 only after configuring the required registrar glue records and confirming that the nameservers work.

Registration and transfer hooks create or associate zones when Auto-Create Zones is enabled. A service termination clears its service association. Deleting a WHMCS domain can delete the actual Bunny.net zone and interrupt DNS. The domain-delete handler attempts provider deletion unless the stored auto-delete value is explicitly off. Confirm disabled-setting behavior on a test installation before using domain deletion as an unlink-only operation.

Associate existing and standalone zones

1. Open the addon and synchronize or create the required zone.
2. Check its domain or service association and owner.
3. For a standalone zone without a domain or service, use the client picker to assign it directly to a client. Search by name, company, email or client ID.
4. Use the Manual (Client) filter to review direct mappings. An orphaned association can be recovered by assigning the zone to the correct client.
5. Sign in as an authorized test client and verify that the zone appears in DNS Management.

A manually mapped zone appears with a Custom badge. Automatic association may replace that mapping with a matching domain or service belonging to the same owner. Do not assign a zone to a client merely because its name looks familiar.

Manage records

Open a zone in DNS Management to add, edit or delete records. Supported types include A, AAAA, CNAME, MX, TXT, SRV, NS, CAA, PTR and TLSA, plus Bunny.net RDR redirects, PZ pull-zone records and SCR script records. These special record types depend on Bunny.net's corresponding features.

The interface validates record values and protects nameserver records. Import a BIND zone file when migrating, or export the existing zone before making bulk changes. Check the resulting records and DNS resolution after an import rather than assuming every source record transferred unchanged.

DNSSEC

1. Enable DNSSEC for the zone in the administrator or customer interface.
2. Copy the displayed DS information, including key tag, algorithm, digest type and digest, to the domain registrar.
3. Check public DNSSEC validation after the registrar change has propagated.

A provider-side enabled status alone does not prove that the registrar DS record is correct. Coordinate DS removal or replacement before disabling DNSSEC or moving authoritative DNS; mismatched DS records can break resolution.

Troubleshooting and upgrades

• For failed API calls, verify the Account API key, cURL and outbound HTTPS to api.bunny.net. Review redacted module and activity logs.
• For missing automatic zones, check module activation, Auto-Create Zones, protected domains and the ownership association.
• For missing customer access, check the domain, service or direct client mapping and the protected-domain list.
• For nameserver errors, check delegation at the registrar and compare public resolver results. Do not assume a fixed propagation time.

Back up the database and module directory before replacing release files. Preserve existing associations and avoid destructive deactivation options. Ask ArkHost support about legacy duplicate hook files before retaining them alongside the current module hooks.