Use the module’s Maintenance and Activity results to diagnose the operation that failed. A zone visible through AWS, a healthy authoritative DNS answer and a working website describe different checks.

Review the affected zone

1. Open AWS Route 53 DNS → Zones and identify the provider/account and domain.
2. Check the client binding, record list and relevant status information.
3. Open Maintenance and review the last task result and time.
4. Inspect Activity for the original action and redacted AWS response.
5. Confirm the normal WHMCS cron is running for scheduled work.

The released health check asks the provider whether a zone exists and what nameservers it reports. It is not an external website, mailbox or certificate test. A warning may need a provider-data review even when public DNS continues serving; confirm public authority and record answers separately.

Run the relevant check deliberately

Use Sync now or the available maintenance action for the intended check. Check whether the task is due, whether it completed and whether its provider credential still permits that action. Do not queue repeated record changes simply because a display has not refreshed.

The module’s optional team alert reports background DNS issues; it is not a substitute for examining the result. Customer notifications and administrator writes are separate from a customer’s own DNS edits. Review saved notification choices before assuming an email should have been sent.

Handle orphaned zones carefully

A zone becomes orphaned when its linked service/domain is cancelled, terminated or removed. Review the saved cleanup and provider-deletion settings before taking action. Stopping module tracking is different from deleting a hosted zone and its records at AWS.

The explicit Delete zone action is destructive; do not treat it as a way to refresh a status. A failed delete can also leave partial changes, so reconcile the live record set before retrying.

Keep the exact zone, action/task time and redacted result for support. For records reported as saved but not visible to visitors, follow the delegation checks before changing credentials or recreating zones.

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 maintenance result

Your hosting team should compare the last task time/result, normal platform cron, provider credential and tracked zone with AWS’s actual zone identity and reported nameservers. Check authoritative DNS and the affected website or mail service separately. For orphan warnings, establish whether the linked domain/service ended and review both tracking cleanup and provider-deletion settings before acting. Do not delete the zone or queue repeated writes to refresh a status.

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