Identify the native rule and its effects before removing a forward through PD Plesk DNS. Website hosting mode, a forwarding mail name and unknown-recipient policy have different removal consequences.

Preserve the current arrangement

Open the intended domain’s Forwarding page and note the rule kind, source, destination and other uses. Review native Plesk hosting and mail settings with the responsible administrator where needed. A BIND record snapshot is not a backup of website configuration or mailbox contents.

For a website forward, removal changes a currently forwarding site to No hosting. It does not restore the website that existed before forwarding was enabled. Prepare the intended next hosting arrangement separately.

For a single-address forward, removal deletes the native mail name. It can affect an existing mailbox or all destinations attached to that name. Do not use this action merely to disable one destination on a multi-use native address.

For a catch-all, removal changes unknown-recipient handling to reject rather than restoring any previous policy.

Remove the intended rule

1. Select the exact provider, domain and rule.
2. Review the confirmation and proceed only after the native effects are understood.
3. Read back the actual forwarding and native hosting/mail state.
4. Test the relevant web or mail behaviour.
5. Inspect remaining rules before adding a replacement.

The module does not delete the native Plesk domain to remove a forward. Domain or subscription deletion is a separate administrator operation with wider service effects.

Reconcile uncertain results

Browsers can retain earlier permanent redirects. Compare current server behaviour separately. If a removal times out, inspect actual native state before retrying or creating another rule.

Retain the rule, original action time and redacted result while your hosting team checks the native state. Do not send API secret keys, mailbox exports or unrelated customer records.

Check the remaining forwarding configuration

Your hosting team should identify the current native hosting mode, mail name and other destinations, or unknown-recipient policy before choosing a removal. Inspect actual state after an error or timeout before repeating it. URL removal changes a currently forwarding site to No hosting; it does not restore the earlier website. Single-address removal deletes the mail name and can affect its mailbox or all destinations. Catch-all removal sets unknown-recipient handling to reject. Have the responsible Plesk administrator prepare the intended replacement. Do not remove a domain or another working rule to clear a warning.

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