Identify the exact native rule before removing a forward through PD DirectAdmin DNS. URL redirects, single-address aliases and catch-all handling have different removal effects.

Review what will change

Open the intended domain’s Forwarding page and note the rule kind, source, destination and any native path reference. Keep the current configuration available for comparison; an ordinary DNS snapshot is not a backup of every forwarding rule.

For a single-address alias created outside the module, inspect all its destinations. The released deletion identifies the source alias, so removing it can remove the complete native alias, not only one receiving address.

Remove and verify

1. Select only the rule you intend to remove.
2. Review the confirmation and complete the removal deliberately.
3. Read back the actual forward list or catch-all state.
4. Test the relevant web or mail behaviour.
5. Inspect remaining rules before adding a replacement.

A URL removal uses the stored source path reference. A catch-all removal resets unknown-recipient handling to failure rather than restoring an arbitrary previous policy. Neither should be treated as the same action as deleting the native domain.

Reconcile cached or uncertain results

Browsers can retain an earlier permanent redirect, so compare current server behaviour separately. If a removal times out, inspect the actual native rule before retrying or adding another one.

The module’s forward-removal requests do not remove the native domain. Native domain removal remains a separate administrator operation and can affect hosting and mail. Keep the exact rule, original action time and redacted result while your hosting team checks the remaining state; do not delete the domain merely to remove a forwarding warning.

Check the remaining forwarding rules

Your hosting team should identify the original URL path reference, source email alias or catch-all mode before choosing a removal. Read the actual native state after an error or timeout before repeating it. A URL removal targets the saved path; an email-alias removal can remove all destinations for that source; catch-all removal switches unknown-recipient handling to failure. Review the intended replacement with your responsible web or mail administrator. The module’s forwarding removal does not remove the native domain; do not delete a hosting domain to clear a warning.

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