- Introduction to Video
- Stream video files
- Start live streaming
- Configure broadcast software
- Live streaming from your app
- Reduce live stream latency
- Manage Stream Keys
- Stream recordings of live streams
- Live streaming FAQs
- Stream live to 3rd party platforms
- Use a custom domain for live streaming
- Handle live stream disconnects
- Stream simulated live
- Debug live stream issues
- Add live captions
- Build real-time video experiences
- Make API requests
- Play your videos
- Enable static MP4 renditions
- Download for offline editing
- Embed videos for social media
- Listen for webhooks
- Secure video playback
- Create clips from your videos
- Get images from a video
- Create timeline hover previews
- Adjust audio levels
- Add watermarks to your videos
- Add subtitles to your videos
- Minimize processing time
- Upload files directly
- Autoplay your videos
- Synchronize video playback
- Integrate with your CMS
Use a custom domain for live streaming
Use your own domain instead of
global-live.mux.com for live streaming ingest. Also known as CNAME-ing or "canonical naming"
In this guide:
CNAME-ing, short for "Canonical Naming", is a configuration that allows you to change the default name we provide.
Mux supports both RTMP and RTMPS entry points. Live streams are published at
RTMP supports using custom domains. Custom domains will not work for RTMPS and
stream.mux.com (playback URLs).
Please reach out to firstname.lastname@example.org with additional details of your requirements.
Here are a few popular domain services with CNAME-ing instructions. If your domain service is not listed, try searching their support resources.
To show an example of a domain service that offers CNAME configurations, this is what a GoDaddy configuration looks like after it has been edited to include the
Note that the CNAME doesn't have to be
global-live, it can be anything you want it to be.
After configuring your DNS settings it may take a few hours before the new configuration works, depending on your DNS provider.
There are a few differences between
- you should see much better performance globally using the new endpoint,
- but it also supports RTMPS. For security reasons RTMPS is greatly preferred (think HTTPS vs HTTP), but some clients may not handle the secure protocol well. For those clients you can specify the port
We don't currently offer a way of creating a CNAME for RTMPS, but you can replicate the existing behavior of
live.mux.com over RTMP with the added port.
Here are a few examples of RTMPS and RTMP CNAME URLs before and after they are changed to custom domains:
# RTMPS examples rtmps://global-live.mux.com:443/app # RTMP examples rtmp://global-live.mux.com:5222/app rtmp://your-cname.your-site.com:5222/app
Please reach out to our Support Team at any time by contacting email@example.com.