How Can We Help You?

Just enter what you are looking for and we will point you in the right direction

HTTP Redirection Record

WHAT ARE HTTP Redirection RECORDS?

The HTTP Redirection record is a combination of A records to Constellix HTTP forwarding servers and a configuration on these forwarding servers. HTTP Redirection records are useful when you want a specific FQDN (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.


HTTP REDIRECTION RECORD FIELDS

Field Description

A) Name This is the hostname for the record, typically a computer or server within your domain. Your domain name is automatically appended to the end of the “Name” field. For example, if you create a record with the name “www” the record would be defined as “www.example.com”.

B) TTL The TTL (Time to Live) in seconds is the length of time the record will cache in resolving name servers and web browsers. The longer the TTL, then remote systems will lookup the DNS record less frequently. Your nameservers will also receive less query traffic since most queries are answered by resolving name servers. Conversely, the shorter the TTL the faster any changes you make to your DNS will propagate in servers that have cached data. However, your domain will receive more query traffic.

Recommended values:

Records that are static and don’t change often should have TTL’s set between 1800 (being on the low end) to 86400 seconds (30 minutes to 1-day cache).

Records configured with Failover or that change often should have TTL’s set anywhere from 180 to 600 (3 to 10 minutes cache).

If a change is needed for a record with a high TTL, then the TTL can be lowered prior to making the change and then raised back up again after the changes were made.


C) 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).


D) 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.

E) 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.

F) Description (optional)

G) URL This will be the destination URL (uniform resource locator) that our forwarding servers will send requests to.

H) Notes Add a helpful note with keywords so you can search for your records later.

I) Save Save your record changes and don’t forget to commit your changes after you’re done making record changes for this domain!

HTTP Redirection