DNS records and browser redirects do different jobs
A DNS record maps a name to a destination such as a server; it does not instruct a browser to open a different URL while preserving a path. A redirect rule is an HTTP response that the edge returns to the visitor. The source therefore needs to be proxied so the edge can see and answer the request.
When you add a rule, the service may create the needed source record and reports whether it did so. A source already configured for DNS-only service is rejected with `redirect_source_not_proxied`. This explicit error prevents the platform from changing the source's delivery behavior without telling you.
Set the destination and path behavior
The redirect destination can be another name in the same domain zone, such as the root name or a subdomain, or an absolute HTTPS address. The default status is 308, and the path and query string are kept unless you turn those options off. Choose settings that match how the destination site expects URLs.
After adding the rule, test the source over HTTPS with a representative path and query string. Confirm the destination, status code, and whether the path and query are preserved. If you remove the redirect, check whether its DNS record was used only for that rule before relying on it for another service.