All Collections
Tips & Tricks
Use custom CNAMES with Videolinq
Use custom CNAMES with Videolinq
Updated over a week ago

A Canonical Name (CNAME) Record is used in the Domain Name System (DNS) to create an alias from one domain name to another domain name. A common example is the www subdomain which is provided as an alias to the root domain name - users accessing "www.example.com" are referred to the root domain (or DNS zone apex) β€œexample.com”.

Videolinq provides this unique service for customers who subscribed to a hosting plan that support CNAME service and want to white label their streaming services when using Videolinq as infrastructure. For example, a customer wants to point to Videolinq, send live video in, and playback live streams or recorded files using Videolinq as a content delivery network (CDN). We support CNAMES for both the stream insertion (RTMP in) and media pull (HLS out streams):

Your path in the live stream encoder can be -

rtmp://myserver.com/application/streamname

When actually, the stream is sent to -

rtmp://videolinq.net/application/streamname

To retrieve the stream you would point to -

https://stream.myserver.com/application/streamname/playlist.m3u8

When actually, the stream will play from -

https://out.videolinq.net/application/streamname/playlist.m3u8

To do this we ask our customers to provide us with:

  1. Two CNAME records they wish to use (for example - rtmp.myserver.com as entry point, and stream.myserver.com as output point). CNAME can only be created by your domain registrar or DNS provider.

  2. A wildcard SSL certificate issued by a recognized SSL certificate authority such as DigiCert, GeoTrust, GoGetSSL, or Sectigo.

This process can take 3 - 14 business days, as it depends on you ordering the SSL certificate from a designated provider. and creating the CNAME with your domain DNS provider. We will complete the setup on our side within 10-14 business days after we receive the SSL certificate and CNAME, as we need to update all our media servers with your SSL certificate.

As you can see, the process to implement CNAME is expensive (purchase of wild-card SSL certificate), and takes time. Please do not request this service unless you are planing to use Videolinq as your CDN (additional data transfer fees applies).

If you want to use this feature and have a Videolinq plan that supports CNAME, please submit a support ticket to begin the setup process. Include the CNAME records you wish to use and a link to download your wild card SSL certificate in a form of JKS + password, or as a Zip file with separate files (key, certificate, CA).

Did this answer your question?