Use Maintenance and Activity to distinguish connection, record validation and server activation failures. The right next action depends on which stage failed; repeated writes do not repair missing server preparation.

Inspect the original action

1. Identify the provider and zone under BIND 9 DNS → Zones.
2. Review available current records and the exact redacted result in Activity.
3. Check the relevant task’s last result and time in Maintenance.
4. Run the provider’s connection test when reachability or required tool access is in question.
5. Confirm the normal Blesta cron for scheduled jobs.

A zone-health check reads the provider zone and reported nameservers. It does not prove public delegation, website availability or a successful signing chain.

Separate the write stages

A candidate rejected by record/zone validation differs from a validated change that was written but could not be activated. If the result says the zone is not being served, ask the BIND administrator to complete server activation rather than rewriting otherwise correct records.

A persistent locking error needs your hosting team’s BIND administrator to inspect the actual operation and server state. Do not remove server locks, files or configuration based on a guessed repair. Reconcile actual record and service state before repeating a timed-out or partly completed operation.

Check jobs and cleanup choices

For backups, verify an actual recent snapshot, not only the configured schedule. Review orphan cleanup, termination retention and provider-deletion choices before acting on a zone linked to a cancelled service.

Explicit Delete zone is destructive provider work, not just removal of a client binding. For editable zones, the administrator must review the server’s remaining serving configuration separately. Retain snapshot references and exact redacted action results while your hosting team checks the actual outcome. Do not send private keys, passwords, full configuration or unrelated client data.

Check scheduled tasks and zone state

Your hosting team and BIND administrator should compare the original operation, current records, Activity and task result to identify connection, validation, file-write, activation or scheduling failure. A lock or reload refusal is not permission to remove server files or repeat a partly completed change. Review actual serving state and any remaining configuration separately from module health and billing state.

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