Why set up a custom CDN domain?
By default, BeyondWords serves audio and video files from a BeyondWords CDN domain. Some organizations, however, require media to be delivered from their own domain. Setting up a custom CDN domain allows your media files to be served from a subdomain you control, such as:bw.yourdomain.com
This is commonly used when:
- Security policies require allow-listing
Some organizations restrict external domains. Serving audio and video from your own subdomain makes it easier to allowlist. - Corporate firewalls or network controls are in place
Internal networks may block unknown CDNs but permit traffic from approved domains. - Brand and domain consistency is preferred
Media assets can appear to come directly from your organization’s domain rather than a third-party domain.
Set up a custom CDN domain
To use themediaHost setting, you must first configure a custom domain with BeyondWords.
This allows you to serve audio and video from your own domain, which can then be allowlisted by enterprise networks.
Add a TXT record for verification
We will provide a TXT record to verify that you own the domain.For example:Add this to your DNS settings.
Add a CNAME record
Once verification is complete, we will provide a CNAME target.Example:This points your subdomain to BeyondWords infrastructure.
Some DNS providers only require the subdomain part (e.g.
bw) rather than the full hostname. Check your provider’s documentation if you are unsure.Wait for DNS propagation
DNS changes can take up to 24–48 hours to propagate, although most updates take effect within a few minutes.
SSL is issued automatically
Once DNS is configured and has propagated:
- The domain is verified
- An SSL certificate is issued automatically
- HTTPS becomes available
How the custom CDN domain works
Media is normally served from:Important notes
- The custom CDN domain only affects audio and video delivery
- You may still need to allowlist:
proxy.beyondwords.io(player script)api.beyondwords.io(API)
- Magic Embed does not automatically switch domains—you must use the
mediaHostsetting