Forward All URL Paths from One Host to Another in UltraDNS

Follow these steps to forward all URL paths from one HTTP host to the same paths on another host. For example, http://www.domain.com/page1 forwards to http://www.domain2.com/page1.

This configuration uses a wildcard in the source URL and Relative Forwarding to preserve the incoming URL path.

How to Create the Web Forward

1. Log into UltraDNS.
2. Click Domains.
3. Click the <domain name> where you want to create the web forward.
4. Under Web Forwarding, click + Add Record.
5. In the Requests To: field, enter the source host followed by a wildcard. For example, enter http://www.domain.com/*.
6. In the Redirects To: field, enter the destination host. For example, enter http://www.domain2.com/.
7. Select the required redirect Type. For example, select 301 Redirect when the redirect is intended to be permanent.
8. Enable Relative Forward and select Path. This appends the incoming URL path to the Redirects To: URL.
9. Click Save.

Additional Information

The wildcard in http://www.domain.com/* is required to match paths below the source host. A source value that contains only the host, such as http://www.domain.com/, does not match every path.

The Path Relative Forward option preserves the incoming path but discards incoming query parameters. If you also need to preserve query parameters, select the Relative Forward option that preserves both the path and parameter.

URL fragments, which are the portions of a URL after #, are not included in HTTP requests and cannot be preserved by a server-side redirect.

If you do not see Web Forwarding, confirm that you are on the Records tab. Open Settings next to Collapse All at the top-right of the records list and confirm that Web Forwarding is selected.

For more information about redirect types and Relative Forwarding, see What are the differences in Redirect Types and using Relative Forwarding?

Verification

• Test a path on the source host, such as http://www.domain.com/page1.
• Confirm that the request forwards to the same path on the destination host, such as http://www.domain2.com/page1.
• Test another path, including a nested path if applicable, to confirm that the wildcard and Relative Forward settings match additional pages.
• Confirm that the returned HTTP redirect status matches the selected Type, such as 301 when 301 Redirect was selected.

Related Articles

• UltraDNS Web Forwarding Guide
• What are the differences in Redirect Types and using Relative Forwarding?
• HTTPS Web Forwarding Account Setup Process