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

Create the DNS allowance

1. Open Plesk DNS → 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. The per-type TTL setting pre-fills the editor; it does not make this version of the module apply an individual TTL.

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

Verify the saved change

Read back the actual record names and values after saving. The module’s displayed TTL can be a fallback rather than the native value. An edit adds the new value before removing the old one, so a failed removal can leave both values present. A requested TTL is not sent by this version of the module; see the TTL guide before relying on a TTL change.

Check the effective allowance

Your hosting team should compare the saved enabled DNS package, linked platform product/package, relevant active services and zone owner with the effective zone/record allowance. Check per-type counts, zone lock, secondary-zone status and content policy separately from quota. Zero and applicable unlimited allowances do not mean a zero-record entitlement. Do not change every limit to unlimited to conceal a wrong product or owner association.

See the PD Plesk DNS Blesta guide for related tasks, or explore the module.