The HTTP redirect service allows you to perform off domain redirects, which means redirecting HTTP traffic from the web server at A.com to the web server at B.com. This works especially well for redirecting from a misspelled domain to your correct domain.
NOTE: HTTP Redirect needs to be added to each node you want redirected. For example, adding the HTTP Redirect service to the apex (i.e. “root”) of your zone will only redirect traffic for the basic domain (e.g. http://example.com); if you want traffic to be redirected for http://www.example.com you will also need to add the HTTP Redirect service to the www node.
If needed, you can also append port numbers to the destination URL. The HTTP redirect service can not be used with other protocols such as HTTPS, SMTP, or FTP. As with all services, only Dyn Managed DNS users who are members of the Owners or Administrators permissions groups are able to create or delete the HTTP Redirect service.
|Adding the HTTP Redirect Service|
|Redirect URL||Enter the full URL (including http:// or https://) of the desired destination. If needed you can append port numbers to the end of the URL, an example would be http://example.com:8080|
|Include requested URI in Redirect||Checking this box appends the requesting URI to the end of the redirect.
NOTE: URI = Uniform Resource Identifier
|For example: Define the redirect URL as
When the user enters
|Response Code||Code 301 is a permanent redirect, meaning that in the future the user will be automatically directed to the new path instead of the original.
Use Code 301 to preserve your SEO link values with search engines.
Code 302 is a found redirect and is a temporary location. In the future the user will be directed to the original path.
Additional Information on the HTTP Redirect Service
|Redirecting Alternate Domains||Also known as off domain redirects.This refers to redirecting domain A.com to B.com|
|Enabling HTTP Redirect during zone creation||If you enable HTTP Redirect Service during the zone creation process two HTTP Redirect services are created. One at the root of the zone and the other as a wildcard entry.|
|Redirecting between different security levels||When redirecting a domain, the security level of each domain involved is important. You CAN redirect a non-secure domain (http://) to a secure domain (https://), but you CANNOT redirect a secure domain (https://). This is by design and is due to the way secure domains (https://) and SSL certificates work.|