Have a Question?

If you have any question you can ask below or enter what you are looking for!

HTTP Redirection Record

These records are not standard DNS records. The HTTP Redirection record is a combination of A records to DNS Made Easy HTTP forwarding servers and a configuration on these forwarding servers. HTTP Redirection records are useful when you would like a specific fully qualified domain name to forward to a URL that may or may not be within the same fully qualified domain name. They are designed to only work with the HTTP protocol.

  • Name: This will be the host for your domain which is actually a computer within your domain. Your domain name is automatically appended to your name. If you are trying to make a record for the system www.example.com. Then all you enter in the text box for the name value is www.
    Note: If you leave the name field blank it will default to be the record for your base domain. The record for your base domain is called the root record or apex record.
  • URL: This will be the destination URL (uniform resource locator) that our forwarding servers will send requests to.
  • Hard Link: When checked, any request that is made for this record will have the path removed after the fully qualified domain name portion of the requested URL. For example, an HTTP Redirection record with the name ‘www’  under the domain ‘example.com’ and a URL of ‘http://www.dnsmadeeasy.com/support/’, a hard link would cause any request for ‘http://www.example.com/some/path/index.html’ to forward to ‘http://www.dnsmadeeasy.com/support/’ and not ‘http://www.dnsmadeeasy.com/support/some/path/index.html’. If Hard Link is unchecked, the same request would forward to ‘http://www.dnsmadeeasy.com/support/some/path/index.html’.
  • Redirect Type: There are currently three options: Hidden Frame Masked, Standard 301, and Standard 302. Choosing the Hidden Frame Masked option under this field will cause the redirection to occur in a hidden iframe within the requesting user agent (for example, your clients web browser). For example, with Hidden Frame Masked set, an HTTP Redirection record with the name ‘www’ under the domain ‘example.com’ and a URL of ‘http://www.dnsmadeeasy.com/support/’ would cause the requesting user agent to continue displaying ‘http://www.example.com’ in the address bar even after redirection has occurred, as opposed to showing the URL that the requesting user agent was redirected to. Choosing the Standard 301 option under this field will cause the redirection to be done as an HTTP 301 Moved Permanently status. This informs the requesting user agent that this redirection is permanent (or long term). Choosing the Standard 302 option under this field will cause the redirection to be done as an HTTP 302 Moved Temporarily status. This informs the requesting user agent that this redirection should be considered temporary (or short term).
  • Title: (optional) If set, the hidden iframe that is used in conjunction with the Hidden Frame Masked Redirect Type will have the HTML meta description data field set to the value of this field.
  • Keywords: (optional) If set, the hidden iframe that is used in conjunction with the Hidden Frame Masked Redirect Type will have the HTML meta keywords data field set to the value of this field.
  • TTL: The TTL (Time to Live) is the amount of time your record will stay in cache on systems requesting your record (resolving name servers, browsers, etc.). The TTL is set in seconds, so 60 is one minute, 1800 is 30 minutes, etc..
    Systems that have a static IP should usually have a TTL of 1800 or higher. Systems that have a dynamic IP should usually have a TTL of 1800 of less.
    The lower the TTL the more often a client will need to query the name servers for your host’s (record’s) IP address this will result in higher query traffic for your domain name. Where as a very high TTL can cause downtime when you need to switch your IPs quickly.
    Best Practice Tip
    If you plan on changing your IP you should set your TTL to a low value a few hours before you make the change. This way you won’t have any downtime during the change. Once your IP is changed you can always raise your TTL to a higher value again.

Example 1 – A standard 301 HTTP Redirection record for www.example.com to the URL http://www.google.com:

NAME TTL TYPE HARD LINK REDIRECT TYPE DATA/URL
www.example.com 1800 HTTPRED Unchecked Standard 301 http://www.google.com

Configuration:

1

HTTPRED record details:

  • Name: www.example.com. is the host which are we are making an entry for. In the data entry screen we only enter www (the domain name will be automatically appended to the end).
  • Data / URL: The destination URL http://www.google.com.
  • Hard Link: Unchecked
  • Redirection Type: Standard 301 Permanent
  • TTL (time to live) – The 1800 indicates how often (in seconds) that this record will be cached in resolving name servers.
  • The end result of this record is that www.example.com. points to http://www.google.com. In the web browser http://www.google.com will display as the URL.

Example 2 – A standard 302 HTTP Redirection record for www.example.com to the URL http://www.google.com:

NAME TTL TYPE HARD LINK REDIRECT TYPE DATA/URL
www.example.com 1800 HTTPRED Unchecked Standard 302 http://www.google.com

Configuration:

2

HTTPRED record details:

  • Name: www.example.com. is the host which are we are making an entry for. In the data entry screen we only enter www (the domain name will be automatically appended to the end).
  • Data / URL: The destination URL http://www.google.com.
  • Hard Link: Unchecked
  • Redirection Type: Standard 302 Temporary. Using a 302 redirection from http://www.example.com/ to http://www.google.com, means that although the page is temporarily redirected to Google, the preferred address to be used in the future remains http://www.example.com/. 302 redirects should be used for temporary redirections. Browsers automatically follow these redirections.
  • The 1800 indicates how often (in seconds) that this record will be cached in resolving name servers.
  • The end result of this record is that www.example.com. points to http://www.google.com. In the web browser http://www.google.com will display as the URL.

Example 3 – A Frame Masked HTTP Redirection record for www.example.com to the URL http://www.google.com:

NAME TTL TYPE HARD LINK REDIRECT TYPE DATA/URL
www.example.com 1800 HTTPRED Unchecked Frame Masked http://www.google.com

Configuration: 

3

HTTPRED record details:

  • Name: www.example.com. is the host which are we are making an entry for. In the data entry screen we only enter www (the domain name will be automatically appended to the end).
  • Data / URL: The destination URL http://www.google.com.
  • Hard Link: Unchecked
  • Redirection Type: Frame Masked
  • TTL (time to live) – The 1800 indicates how often (in seconds) that this record will be cached in resolving name servers.
  • The end result of this record is that www.example.com. points to http://www.google.com. In the web browser http://www.example.com will display as the URL.

Example 4 – A standard 301 HTTP Redirection record with Hard Link for www.example.com to the URL http://www.google.com:

NAME TTL TYPE HARD LINK REDIRECT TYPE DATA/URL
www.example.com 1800 HTTPRED Checked Standard 301 http://www.google.com

Configuration:

4

HTTPRED record details:

  • Name: www.example.com. is the host which are we are making an entry for. In the data entry screen we only enter www (the domain name will be automatically appended to the end).
  • Data / URL: The destination URL http://www.google.com.
  • Hard Link: Checked
  • Redirection Type: Standard
  • TTL (time to live) – The 1800 indicates how often (in seconds) that this record will be cached in resolving name servers.
  • The end result of this record is that www.example.com. points to http://www.google.com. In the web browser http://www.google.com will display as the URL. If the end client types www.example.comm the redirect will function and in the web browser http://www.google.com will display as the URL. Any trailing text after the www.example.com will be ignored.