What are HTTP Redirection Records?
Types of Redirects
Permanent Redirect (301)
Temporary Redirect (302)
Hidden Frame Redirect
1.Select Managed DNS and click on Domains
2. Select the Domain Name you want to add an HTTP Redirection record too.
HTTP REDIRECTION RECORD FIELDS
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.music.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 name servers 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.
C) Redirect Type: There are currently three options: Hidden Frame Masked, Standard 301, and Standard 302.
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 too.
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!
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.