The module's Plesk integration uses administrator API access, with REST and XML operations as required by the driver. Use HTTPS and a valid server certificate. Prefer a suitably managed API key and restrict its source address where your Plesk configuration permits it.

Confirm that the target subscription exists and is active. Decide how its web content, SSL certificates and mail behaviour should apply to aliases. A DNS-only offer should not accidentally imply that customers receive independent hosting accounts.

1. Open DNS Manager > Servers and edit the Plesk connection.
2. Complete the server endpoint and credential fields shown by the Plesk driver.
3. Set the optional Plesk Subscription Domain to the existing subscription's domain.
4. Save, run the connection test and create a new controlled domain through the intended DNS package.
5. Verify the alias target in Plesk, inspect its DNS records and test the expected web and mail behaviour.

The new-alias workflow does not mean every existing Plesk site can be converted automatically into a parked DNS-only domain. Existing sites may have separate owners, content, certificates and mail settings. Do not generalise the cPanel background conversion of eligible standalone zones to Plesk websites.

When an existing domain conflicts with a new alias, identify its actual Plesk object and owner. Resolve the conflict through a planned hosting or domain migration rather than deleting a live subscription.

The registrar's delegated nameservers determine which DNS network answers publicly. Plesk can contain a correctly configured alias while visitors still resolve another provider's zone. Query the authoritative A and AAAA records, then test the destination web server and certificate.

If email is hosted elsewhere, retain its exact MX and related TXT records and check local mail handling on the alias arrangement. DNS records and Plesk mail-service configuration affect different parts of delivery.

If the customer purchases hosting for the parked domain, review the optional hosting-transition integration and its owner/server checks. It is a controlled handoff around WHMCS provisioning, not a general transfer of arbitrary subscriptions or another customer's website.

• Preserve DNS when a parked domain becomes a hosting account
• Use a cPanel account username as the owner of parked DNS domains
• Add a DNS provider connection and prove that it can manage zones
• Point your domain to a website without disrupting business email
• Configure domain and email forwarding as separate services

• Plesk: About REST API
• Plesk: Secret key authentication