Use PD DirectAdmin DNS’s URL forwarding controls for a prepared domain that exists in the provider’s account context. A redirect is an HTTP response from the web service, not the same thing as an ordinary DNS alias.

Prepare DNS and web service

Confirm the intended domain is visible through the provider and its web service can handle the redirect. DNS must direct source visits to that infrastructure, and HTTPS needs a valid source certificate. The module does not supply free SSL for this provider.

Review existing hosting and records before acknowledging a coexistence warning. Do not use Forward anyway if it conflicts with hosting/records merely to clear an unexplained warning.

Add and inspect the redirect

1. Open the domain’s Forwarding page and add a URL forward.
2. Review Forward this host and enter the complete destination under To this URL.
3. Choose the intended 301 — Permanent, 302 — Temporary or 303 — Replaced option.
4. Create the forward and read back its destination and status.
5. Test the actual root, path/query and HTTPS visits that matter for this domain.

New module-created forwards use the domain-root source path. This provider does not offer www or wildcard switches through its forwarding capability. Existing native path redirects can be listed, but do not assume the shared host field selects an arbitrary new source path.

Check path behaviour explicitly

The shared form may show Keep the path, but the released DirectAdmin write does not pass that preference as a path-preservation setting. Do not rely on toggling it to change server behaviour. Use the administrator’s supported native redirect controls for a more specific path requirement.

Check the live HTTP result separately from a saved module rule, and account for browsers caching older permanent redirects. Retain the source, destination, status, original time and redacted result while your hosting team checks the actual response.

Check the redirect

Your hosting team should compare the selected native domain, saved source-path reference, full target URL and status with the actual HTTP response. Check authoritative DNS, source HTTPS and cached permanent redirects separately from the module’s saved rule. New module-created rules use the root path, and the shared Keep the path preference is not passed as a preservation setting to this provider. Use your DirectAdmin administrator’s native redirect controls for a source-path requirement the module does not offer; do not bypass a coexistence warning to diagnose it.

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