WHMCS domain synchronisation updates local domain information from the connector's confirmed upstream state. Keep it running so a pending registration or transfer can become active and expiry dates can follow the registry outcome.
01 Configure the normal sync task
- Confirm the domain is assigned to the installed Domain Nexus registrar connector.
- Check that the normal WHMCS system cron runs under the intended PHP environment and can reach the current HTTPS API endpoint.
- Open System Settings > Automation Settings and review Domain Sync Enabled, the expiry and pending-transfer frequencies, and any notify-only setting.
- Decide deliberately whether WHMCS should synchronise the customer's next due date. A billing due date can have a different purpose from the registry expiry date.
- Review the next task report and one representative domain's local status and expiry.
02 Investigate a pending domain
The connector implements separate normal and transfer synchronisation callbacks. Read the existing upstream domain or transfer operation and compare it with the local record. A provider transaction still processing cannot be made complete by changing the local label.
If the upstream operation has completed but WHMCS is unchanged, check the cron report, registrar assignment, authentication from the worker and whether notify-only is enabled. WHMCS processes domain checks in batches, so a newly changed domain may not be the next active record checked.
For a failed transfer, inspect its specific reason, authorisation code requirements, source lock and customer verification. Avoid repeatedly creating new transfer orders while the original remains unresolved.
Common questions
Should I manually set Active after payment?
Payment is not registry confirmation. Confirm the provider result and use the normal synchronisation or supported reconciliation process.
Why does the expiry date differ from the next due date?
The expiry reflects registration validity. The next due date belongs to billing. Review the intended renewal lead time and sync setting before making them identical.
Does this task update nameserver delegation at the registry?
Synchronisation reads domain state through the connector. An intentional nameserver change uses its separate management operation.
When escalating, include the domain, connector version, last successful cron time, operation ID and redacted sync error. Keep API keys and EPP codes out of the report.
Related articles
- Synchronize a domain's current provider state through the v2 API
- Monitor and reconcile a pending domain transfer through the v2 API
- Follow a domain operation through pending, failed and manual-review states
- Investigate a WHMCS connector order blocked by reseller account status
- Preview and schedule exact domain price imports from the command line