In the audited package controls, a zone or record limit of -1 means unlimited and 0 blocks that resource. A backup retention value of 0 disables retained backups. Do not use zero as a shorthand for unlimited or assume every numerical setting has the same meaning.

Plan limits should reflect the service you sell and the provider's own limits. A large module allowance cannot override a vendor account quota. Review existing usage before reducing limits so support can explain which new actions will be refused.

1. Open the relevant DNS package and review its general controls.
2. Select DNS and reverse DNS, DNS only, reverse DNS only or read-only management as appropriate.
3. Configure allowed record types and the actions customers may use, including import, export, record sets, DNSSEC and backups.
4. Review server capabilities and IP policy. A package permission can allow an action only when the zone's provider and ownership rules also support it.
5. Save and test with a customer assigned to the package. Administrator pages may expose controls that a customer cannot use.

Check the customer's current qualifying product, addon or domain, the resolved package and the zone's ownership. Next compare the action with package policy, record protection and the backend capability. For reverse DNS, verify actual assigned IP ownership; a forward A record alone is insufficient.

If a customer can read but cannot edit, inspect the management mode, account permissions, delegation requirements and any protected record. If importing fails at a limit, preview the final record count rather than counting only the file's new lines. Duplicate records and provider-managed entries can affect what will be accepted.

Use a test package for major policy revisions. Record why an override exists and review it when the underlying subscription changes. Avoid granting broad administrator privileges merely to resolve one customer action.

Update your customer documentation when a feature becomes available or is withdrawn. A help article can explain a conditional feature, but the purchased package and the current controls determine the customer's actual entitlement.

• Build a DNS package for hosting products, addons and domain TLDs
• Review customer DNSSEC and reverse DNS requests
• Delegate reverse DNS only for addresses a customer actually holds
• Fix missing DNS controls, read-only zones and limit messages