Use the module’s Packages area to link a DNS allowance to the Blesta packages you sell. Module allowances control client management; they do not increase AWS hosted-zone or record quotas.

Define the offering

1. Open AWS Route 53 DNS → Packages.
2. Create a recognisable DNS allowance package.
3. Review the zone allowance, records-per-zone cap and any per-type rules offered by the form.
4. Link it to the intended Blesta packages and enable it.
5. Check the linked active service and intended zone owner before relying on enforcement.

A default TTL for a type pre-fills future edits; it does not rewrite all previously published records. Read zero/unlimited settings carefully before saving a commercial tier.

Check the effective allowance

The released logic considers applicable packages behind active services. It uses the largest applicable finite allowance, rather than adding each service’s quota together. An applicable unlimited allowance removes the corresponding finite cap.

Confirm the customer owns the zone and that the active service is actually linked to the product/package you selected. Do not use an unowned zone or an unrelated account to conclude that entitlement enforcement is working.

Diagnose a refused operation

Compare the current record count and module allowance with AWS’s separate provider quota. A record change can also be refused by IAM policy, a zone lock, content rules or a protected managed record. Identify the actual cause before changing an allowance.

Do not delete working records just to clear a limit warning. Review whether the DNS tier matches the service sold and adjust the intended configuration. Disabling a module allowance is not a request to delete the customer’s DNS records.

For a zone that is not visible, start with the ownership/access guide; for a failing background create, use the automatic-zone guide. Keep the redacted error and relevant settings for support without exporting unrelated customer data.

Check same-named hosted zones before changes

If your AWS account contains multiple hosted zones with the same domain name, do not assume choosing a same-named row selects a particular hosted-zone ID. This module resolves zones by name. Have your AWS administrator compare the exact hosted-zone ID, records and delegated nameservers before using module writes; use AWS’s native zone-specific controls if the target remains ambiguous. Do not create or delete another zone to diagnose that ambiguity.

Check the effective allowance

Your hosting team should compare zone ownership, linked active services and applicable enabled packages with the effective allowance. Check the largest applicable finite limit or unlimited setting separately from AWS quotas, IAM refusals, locks and protected records. The import preflight checks the planned input against the owning customer’s record allowance before writing; changing a package does not repair an AWS permission refusal. Do not delete working records to test an allowance.

See the PD AWS Route 53 DNS Blesta guide for related tasks, or explore the module.