Connect the provider you already use, then adopt its zones in PD DNS Manager. Tracking a zone and changing its authoritative nameservers are separate tasks: adoption links management to the intended client without moving its records.

Before a change, confirm the provider connection and the actual zone it resolves. With Route 53, name-based operations resolve the first matching hosted-zone name; selecting a familiar domain is not sufficient when AWS holds multiple zones with that name. Have your AWS administrator compare the hosted-zone ID, records and assigned nameservers before proceeding. With Google Cloud DNS, the current connection derives the managed-zone name from the domain. An existing zone with a different native name can appear in a list yet fail to open correctly; establish that mapping with your Google Cloud administrator instead of creating a duplicate zone.

Review the matches

1. Open DNS → Zones and select the intended provider.
2. Review Untracked zones found and the corresponding active domain or hosting service.
3. Use Track for one zone, or Track matched zones after reviewing the matching set.
4. Check the Client and Bound to entries before enabling customer editing.
5. Open the zone and confirm it is the provider copy you intended to manage.

Matched adoption leaves the provider’s DNS records alone. An unmatched zone is not proof of an error: it may belong to another account or have no corresponding active service here. Do not recreate it merely to make a client link appear.

Assign a zone manually

For a legitimate custom domain with no automatic match, use the zone menu’s Assign to client action. Select the intended account and review its ownership. Verify the binding before directing the customer to their DNS area.

Customers can reach their zone through My Tools in the client portal, then the DNS manager. Where enabled, the module also has a direct client-menu link using the label configured by your hosting team. Check the saved navigation choice. The available record, backup, import and signing controls depend on provider support and your saved access policy.

Restrict editing deliberately

Use Lock while investigating a zone and Unlock when customer editing should resume. A lock affects client writes; administrators retain their own management controls. The DNS record editing for domain-only customers setting separately permits full editing, view-only access or hidden record pages for customers with a registered domain and no hosting service here.

If a zone is missing from the customer’s view, check ownership, active service, tracking, lock and visibility separately. Removing a binding withdraws access without being a request to delete the provider zone. See the content-policy guide for refused saves.

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