Find answers to common questions about CDN integration and domain management in RMS.

In this article:

1. CDN configuration

2. Domain and endpoint management

For core concepts and best practices, refer to:

• CDN and custom domains in RMS - an overview page
• Streaming origin endpoint: Best practices - Streaming origin setup and configuration
• Front Door Endpoint: Key details - Front Door usage guidelines

1. CDN configuration

Can I enable caching in my RMS Front Door instead of using an additional CDN?

Yes, Ravnur can take care of this. It is the most cost-effective way to set up a CDN for your RMS cluster, with the additional benefit of making the Streaming Origin Endpoint private.

How to integrate a custom CDN with the RMS streaming endpoint?

• Map your CDN to the streaming origin endpoint.
• Do not map it to the RMS Front Door endpoint. According to Microsoft's documentation, this is considered a bad practice.
• Use the Ignore Query String option for efficient caching.
  • To understand the impact, consider the following example URLs:

  • https://domain/path/master.m3u8?token=token1

When Ignore Query String is enabled, the CDN will ignore anything after the "?" when caching content. This means the same cached response will be served regardless of parameters liketoken=token1 or token=token2, learn more.

• No other configurations are required.
• Update the streaming endpoint Host name in the RMS Console

What is the default cache TTL for RMS content?

Time-to-live (TTL) functionality allows the database to automatically expire data.

The default cache values are:

• 100 days for VOD content;
• 6 days for downloads.

Ravnur can adjust these settings as needed; however, downloads cannot be cached for more than 7 days.

Note: We do not recommend overriding cache settings on your CDN. The streaming server will automatically determine the best way to cache content.

How to choose a CDN provider?

Based on infrastructure requirements, we suggest the following options:

• Azure Front Door: Not optimal for media streaming, but it can hide the origin endpoint.
• Azure Standard CDN (classic): More efficient for media delivery and also allows hiding the origin endpoint from public access. However, it will be retired in 2027.
• Fastly: More efficient than the previous options or Azure Front Door. Drawbacks: limited point-of-presence (POP) availability in some regions and no ability to hide the origin endpoint from public access.
• Akamai: High delivery performance and global reach with the largest POP network. Drawbacks: higher cost tier and no ability to hide the origin endpoint from public access.

2. Domain and endpoint management

How to use a custom domain with the RMS Front Door?

1. Create a CNAME record for the alias host domain to point to the RMS native Front Door Endpoint: fd-{unique string}.{AFD DNS subdomain}.azurefd.net. Refer to the guidelines for obtaining the RMS Front Door domain and the instructions for creating and mapping a CNAME in Azure Front Door.
2. Submit an RMS support request to add your custom domain name to the RMS Front Door. When contacting RMS support, provide:

• Your domain name.
• The RMS resource group.

3. Update your Streaming Endpoint host name in the RMS console 👇.

How to update the RMS streaming endpoint host name?

1. Go to the RMS Console.
2. Select Account settings tab> Streaming Endpoints.

3. Change the Host Name field and Save :  

   

If your application uses static URLs or stores the streaming domain in its configuration, make sure to:

• Update all static URLs for streaming links whenever changes are made.
• Modify the application’s configuration to reflect the updated streaming domain.

Why do I need to update the streaming endpoint host name in the RMS Console?

It depends upon how the application accesses the domain name for streaming links:

• If your application uses the RMS API (common option):

Applications that request the RMS API for the domain name used in streaming links need this update. The API will use the updated domain name when generating streaming links.

• If your application uses local configuration:

Applications that store the domain name in their own configuration do not require changes in the RMS Console. Update the domain name directly in your application's configuration.

Have more questions? Contact Ravnur Support at support@ravnur.com or explore the Knowledge Base.