1. Record the affected provider connection, zones, task references and first observed time.
2. Check whether other connections to the same provider are affected. Compare the provider's current status information with your own observations.
3. Query the existing authoritative nameservers for a known record. Separately inspect the module's connection or task error.
4. Pause new bulk work under your operational procedure so the queue does not fill with repeated attempts at the same change.
5. Preserve the desired record set and a last-known provider snapshot. Do not replace failed reads with an assumed empty zone.

When access returns, read the actual provider state before resubmitting uncertain work. A provider may have accepted a write even though its response never reached WHMCS. Use reconciliation and the existing task's recovery path to decide whether the change is already present, still pending or genuinely failed.

For a package replicated across multiple servers, inspect each target's result. One healthy target does not prove every target is current. Keep the intended master and delegation under review; do not remove a failing target's remote zone just to clear a status message.

Only a prepared replacement with complete records and a reviewed DNSSEC plan offers a sound migration path. Changing delegation to an empty backup can turn a management incident into a website and mail outage. Resolver caches also mean a delegation change is not instant failover.

Provide the connection label, affected domain, approximate time, task or request identifier and observed authoritative answers. Include the provider error code when available. Keep tokens, full authenticated URLs and secret-bearing request headers out of tickets. Describe whether an operation was submitted once or retried, so the outcome can be reconciled accurately.

• Resolve DNS drift and changes with an unknown provider outcome
• Coordinate provider API quotas across web requests and background workers
• Move managed zones to another DNS provider with a verified rollback point
• Collect useful details when a DNS change is not working