To install the ClouDNS DNS Manager module you need to place the module folder in the servers directory of your WHMCS installation. Example:
CREATE TABLE IF NOT EXISTS `mod_cloudns_zones` (
To configure the ClouDNS DNS Manager module you just need to open the file /path/to/whmcs/modules/servers/cloudns/cloudns_core/configuration.php and enter your ClouDNS API auth-id and auth-password on lines 9 and 10.
public static $_apiAuthId = 0; // your ClouDNS API ID
If you want all the products to use the same server names for NS records of zones by default you can add them in the below block in the same configuration file and uncomment it removing the "/*" and "*/" surrounding the server names.
public static $_DnsServers = array(
Note: If you want to set different server names per product you need to leave this block commented and add the server names from the module configuration in the admin panel of the particular Product/Service.
If you don't already have a Product to use the module with you can create one from Setup > Products/Services > Products/Services and click on the Create a new product link.
Suspension and termination of products
This module does not change the behavior of the suspension/termination of a product/service in WHMCS.
1. A product will be suspended automatically (if you enabled the WHMCS cron) if the product is not free e.g. the Recurring Amount is higher than 0, the Billing Cycle is not Free or One Time and the Next Due Date is at least 5 days ago.
2. When a product is suspended the DNS zones of the customer will be inactive and the DNS servers will return only NS records for them.
3. If a product is terminated the DNS zones of the customer will be deleted from the ClouDNS system and the DNS servers will return empty responses for them.
4. If you manually unsuspend (read below) a product the zones of the customer will begin working again if the product was suspended. If the product was terminated the zones will remain deleted.
5. Manual suspend/unsuspend/termination can be done via the corresponding buttons in the Module Commands section of the Product/Service's control panel. Manually doing one of this things will result in the same way as the automatic action.
The module is tested with versions 5, 6 and 7 and should work with them without any problems. However some differences in the design are possible.