DNS Mask our Content Servers

Purpose

This guide explains what DNS masking is and how to DNS mask our content servers (content.bitsontherun.com)

What is DNS masking?

With DNS masking you can make it look like the Bits on the Run embed codes are part of your domain instead of hosted on a third party service. People looking in your HTML code will see e.g. cdn.example.com instead of content.bitsontherun.com.

It also means that, if you have enabled the sharing plugin, the shared embed codes will contain your own domain name. This looks more professional towards your customers.

Player embeds (script, iframe, embed), preview thumbnails, RSS feeds and video downloads all benefit from DNS Masking.

1: Setup a DNS Mask

Technically, DNS masking is accomplished by setting up a CNAME record. You have to do this yourself with the company that manages your domain name. We cannot do this for you.

Each domain provider has a different interface, but the example below (for Media Temple) should give an indication of how the the DNS mask should look:

• Note you do not have to use a subdomain called content. You can use any string (e.g. video or cdn).
• Also note the record type should be CNAME.
• Last, the dot after content.bitsontherun.com. is required. Don't forget it!

It can take up to a couple of hours for the new CNAME record to propagate. Once it has completed you should see your data load if you replace our domain name with yours. Here's a simple example image to test.

2: Register a DNS Mask

Once the DNS mask is active, you should submit it to our dashboard, so we can start using the mask for your account. The DNS Mask option can be found in the Account section of the dashboard:

With the DNS mask registered with us:

• The embed codes in all publish dialogs in the dashboard (players, downloads, feeds) will then use your domain.
• The embed codes in the sharing dialog in your players will then use your domain.

After having entered the DNS mask in the Dashboard, you're all set!