Use the module’s Packages area to link a DNS allowance to your Blesta packages. Module limits control client management; they do not raise quotas in the Google Cloud project.

Create and link the intended allowance

1. Open Google Cloud DNS → Packages and choose Add package.
2. Set a recognisable name and zone allowance.
3. Review records-per-zone limits and any per-type rules offered by the form.
4. Link the intended Blesta packages using the package’s picker.
5. Save, enable and verify an applicable active service and zone owner.

Link the actual products/packages rather than assuming a whole product group inherits the settings. Read zero/unlimited values carefully. Default TTL rules pre-fill edits; they do not rewrite previously published record sets.

Check effective entitlement

The released logic considers applicable enabled allowances behind active services. Finite limits use the largest applicable allowance, not the sum of every service’s quota. An applicable unlimited allowance removes the corresponding finite cap.

Confirm the service is active and linked to the configured offering, and the zone belongs to that customer. An unowned zone is not a useful test that a client limit works.

Diagnose the refused operation

Compare the module count and effective allowance with the project’s separate provider quota. Import checks the planned missing records against the owning customer’s allowance before starting; a later provider refusal is a separate failure. A lock, content policy, managed-record rule or Google Cloud permission can also refuse a write.

Do not delete working records merely to clear a cap warning. Review whether the configured DNS tier matches the service being supplied, then make the intended setting correction. Disabling an allowance is not a request to delete provider DNS.

For missing portal access, use the assignment guide. For a zone that cannot be opened at the provider connection, use the identity checks. Keep relevant settings and the exact redacted result for support without exporting another customer’s records.

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