HTTP redirects operate very differently from traditional DNS records. That’s because they require the help of a dedicated web server to store all of the redirects.

When you create an HTTP redirection record, you’re actually making an A record that points to that web server. The web server will respond with a 301 redirect and the destination URL.

You can use HTTP redirects records to redirect traffic to another FQDN (Fully Qualified Domain Name) outside of your domain’s zone.

Constellix does not support HTTPS redirection records. You will have to configure it on your web servers directly where the SSL cert is being managed. You can read more about how they work here.

Types of Redirects

When you create an HTTP redirection record, you will have a couple options to customize the redirect.

Permanent Redirect (301)

Exactly what it says. This is the standard for most redirects.

Temporary Redirect (302)

Tells search engines that you may change it later, so they should check again.

Hidden Frame Redirect

This kind of redirect actually creates a “framed” experience in the browser using a hidden iframe within the requesting user agent (for example, your client’s web browser). The user will see the original URL in their browser but will see the content from the destination URL.

Hard link

You can also configure a hidden frame redirect to not include the path the user entered into their browser.

For example:

Say a user enters www.domain.com/my-blog into their browser

You have a hidden frame redirect set up that will show the original URL in their browser, but show the content for www.notmydomain.com.

A hard link will remove the path “my-blog” from the end of the URL and not append it to www.notmydomain.com.

Meta Tags

You also have the option to configure the meta tags for the framed page.


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.

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

Was this article helpful to you?

Comments are closed.