1. Open DNS Manager > DNS packages and create or edit the package. Complete its general identity and customer-facing description.
2. Choose a management mode and limits that match the offer. Decide whether customers may manage DNS, reverse DNS, both or only read the zone.
3. Open Items and attach the actual WHMCS products, product addons or domain TLDs that should grant this package. Search the existing catalogue rather than entering a name that is not a real WHMCS item.
4. Open Servers, select the provider connections and designate one master. If using multiple servers, explicitly enable synchronization only after reviewing the replication guide.
5. Review Records, notifications, registrar settings and IP policy. Select the default record set and the customer controls you intend to offer.

An item belongs to one DNS package at a time, and the free-zone allowance has its own package assignment. Check these relationships before moving a product between packages, especially when existing customers already depend on its DNS service.

The package can respond to product or addon activation, domain DNS Management addons, registration or transfer stages and reconciliation of existing customers. Select the trigger that matches when your company can establish ownership and prepare the zone. Creating a zone before registration completes should not be presented as proof that the registration succeeded.

Decide whether existing zones should be adopted, missing zones should be created and custom domains should be allowed. A registered-domain TLD entitlement is checked against the customer's actual domain records. It is not permission to claim any external domain ending in that TLD.

Use a test customer and a qualifying item. Confirm that the correct package appears, a zone is created or adopted as intended, the default records are correct and customer controls match the policy. Test a customer without the item to verify access is refused.

If you require delegation before editing, test a domain on external nameservers and document the resulting restriction. If you permit preparation before delegation, teach customers to copy all website, mail and verification records before changing nameservers.

Decide how suspension, termination and removal of qualifying items affect DNS. Protection settings can prevent unsafe cleanup, so a cancelled product does not always mean a zone should disappear immediately. Review lifecycle jobs and customer ownership before deleting a zone that may also support email or another active service.

• Set DNS package limits and customer permissions without blocking the wrong service
• Create DNS record sets that become package defaults
• Synchronize a DNS package across multiple servers and select its master
• Configure DNS lifecycle cleanup with grace periods and protected zones