Use PD PowerDNS’s DNS packages to control the zone and record allowances included with your Blesta packages. These allowances are separate from upstream PowerDNS access and infrastructure capacity.

Create the DNS allowance

1. Open PowerDNS → Packages and add a named package.
2. Set Zone allowance and Records per zone.
3. Review the optional per-record-type caps and default TTLs.
4. Save it with Enabled selected where the allowance should apply.
5. Edit the saved package and link the intended packages.

The package form uses zero for an unlimited allowance; a per-type TTL left at zero uses the standard default. Review those meanings before saving a restrictive plan.

Check effective entitlement

The allowance follows the customer’s relevant active services. Where more than one enabled DNS package applies, the effective limits use the applicable maximum rather than adding each allowance together. Confirm the intended product/package link and client ownership before diagnosing a quota refusal.

Do not treat a DNS package as an upstream per-zone credential or network restriction. A saved allowance also does not create every customer’s zone or change registrar delegation.

Investigate a refused edit

Check the active service, linked enabled package, zone ownership, total/per-type counts and any lock or content policy. A secondary zone remains read-only regardless of allowance. Shared TTL rules still apply to a PowerDNS name/type set.

Retain the relevant allowance and exact redacted refusal while your hosting team checks the effective entitlement. Do not set everything unlimited simply to conceal an incorrect binding; use the client-access guide to check that separately.

Check the effective allowance

Your hosting team should compare the affected customer’s active service, linked enabled DNS package, effective zone/record/type allowance and current module counts with the original refusal. Review ownership, lock, secondary status and content policy separately from entitlement; increasing an allowance does not repair a wrong association or an API refusal. Module record counts are not a complete native-server inventory or capacity measurement. Do not set all limits to unlimited to bypass diagnosis.

See the PD PowerDNS Blesta guide for related tasks, or explore PD PowerDNS.