Use PD Plesk DNS to set a standard website redirect for a domain already prepared in Plesk. This changes the native site’s hosting type; it is not simply an A or CNAME record.

Review the hosting effect first

Confirm the intended domain exists and is available to the provider connection. Review its current hosting, DNS, website and certificate with the responsible administrator. A domain listed for DNS management does not prove every native forwarding operation is available for it.

Plesk’s hosting-type reference explains the difference between website hosting, forwarding and no hosting. Do not convert an active website merely to dismiss a forwarding warning.

Create the intended forward

1. Open the intended zone’s Forwarding page and add a URL forward.
2. Use the domain itself as the source and enter the complete intended destination URL.
3. Choose 301 for an intended permanent move or 302 for a temporary redirect.
4. Read any coexistence warning and proceed only when the hosting change is intended.
5. Save and read back the exact destination and response type.

This provider uses native standard forwarding for the site. It does not offer separate www, wildcard or path-preservation switches through the module. Do not use the shared source field to assume an arbitrary subdomain or per-path redirect is created.

Test as a visitor

Check source DNS, HTTP redirect response and destination separately. Test HTTPS with a valid source-domain certificate; a saved rule is not evidence that a certificate was issued. Check an actual path and query if that behaviour matters rather than assuming they are preserved.

If Plesk refuses the operation, retain the redacted result and have the administrator check the native site/hosting arrangement before retrying. Removing this forward sets No hosting, not the former website configuration; use the removal guide first.

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