Check native domain existence and provider scope before creating or restoring DNS that appears missing in PD Plesk DNS. The module lists subscription main domains and additional sites, then combines the results by name.

Check the intended server and scope

1. Open Plesk DNS → Providers and identify the intended hostname and connection.
2. Run Test connection and inspect any refusal.
3. Confirm the domain exists in that Plesk server under the intended subscription or account.
4. Search Zones with the correct provider and client filters selected.
5. Open a known domain’s records and compare with Plesk’s own DNS view.

The connection test reads server information. A passed test does not prove the key can list every subscription or site. Have the administrator check the exact account and operation; do not replace a restricted credential solely to reveal unrelated customer domains.

Distinguish a domain list from working DNS

A listed domain is not proof that Plesk is authoritative for it. Check that DNS is enabled for the intended domain, whether it is primary or secondary, and which nameservers the registrar delegates to. A subdomain can use its parent’s zone rather than a separate native zone.

When the zone lookup lacks nameserver metadata, the health check also reads apex NS records. A missing-nameserver warning needs a separate native and public authority check before treating working DNS as broken.

Recover only what is actually absent

Changing the client binding does not move the Plesk subscription or expand provider permissions. If the native domain was removed, its approved restoration belongs with the responsible server administrator before module record recovery.

Use the existing-domain management guide when native DNS is ready, or the removed-domain recovery guide when it is genuinely absent. Retain the provider, intended domain, original action time and redacted result while your hosting team checks visibility, without keys or unrelated account exports.

Check the visible domains

Your hosting team should compare the selected server, provider/client filters and native subscription or additional-site ownership with the connection’s account scope. Confirm a known-domain read and whether native DNS is enabled, primary or secondary; a subdomain may use its parent’s zone. A passed server-information test does not establish access to every domain. Do not create a duplicate subscription or restore over working DNS merely to make a list match.

See the PD Plesk DNS WHMCS guide for related tasks, or explore the module.