Add the correct provider connection and ensure its credential can list the intended zones. Confirm the relevant WHMCS products, domains and customers are current. A zone name matching a customer domain is useful evidence, but conflicting ownership or a different hosting account must be resolved before management is granted.

1. Open Servers and run the discovery action for the required connection. The server inventory reads zone names; it does not by itself change records, ownership or bindings.
2. Open Discovery & sync to review the discovered inventory and available linking or import actions.
3. Check each proposed zone against the current WHMCS domain or hosting service, customer and package. Pay attention to existing zones owned by another account or imported through a different connection.
4. Import or link the verified selection using the screen's reviewed workflow. Begin with a small set of controlled domains before a large migration.
5. Open the resulting customer zone and confirm the provider binding, records and customer access.

A package can reconcile existing customers and create missing eligible zones once. Enable this only after its item mappings, servers, defaults and ownership rules are correct. Reconciliation is not a request to create zones for every domain string found in a billing database.

For an externally registered custom domain, follow the supported ownership verification process. Do not grant control simply because a customer can type the name or add an A record elsewhere.

Imported records may describe a zone on a server that is no longer authoritative. Query the current parent delegation and each authoritative nameserver. Importing the stored zone does not move the registrar nameservers or repair an old DS record.

When multiple providers contain different versions, choose the intended source explicitly. Keep exports of both sides before replacing records. Differences may represent a planned migration or an external administrator's legitimate changes.

Leave disputed or incomplete matches unassigned and investigate the customer, provider account and service history. DNS timeouts are not evidence that a zone is abandoned. Record the reason for any manual ownership correction so later cleanup and support work can rely on it.

Confirm the active WHMCS customer and service mapping before linking the zone. An API credential that can list the provider account proves technical visibility, not permission to assign every listed zone to a customer.

• Build a DNS package for hosting products, addons and domain TLDs
• Add a DNS provider connection and prove that it can manage zones
• Configure DNS lifecycle cleanup with grace periods and protected zones
• Add a domain registered elsewhere to your DNS Manager