In this guide
Two discussions, “LionOTT: Custom domain?” from January 2025 and “Lion Panel – Custom Domain” from February 2025, ask about branded addresses for customer connections. Replies suggest several approaches, including supplier assistance and DNS aliases.
Those replies do not verify a feature on every Lion OTT account. They also do not establish that pointing a domain at a service is sufficient for HTTPS or player compatibility. Use the following sequence as a planning and troubleshooting checklist, not as confirmation that a particular supplier enables custom domains.
List the purpose before requesting a DNS target:
One branded hostname is not automatically interchangeable with all three. Ask the supplier which connection format is supported. Our account format guide helps you record the device and input method before setup.
Send this request through your existing supplier contact:
“I want to use a hostname on a domain I control. Is this supported on my account? Please confirm the approved DNS target, whether you must register the hostname, the supported protocol and port, who provides the HTTPS certificate, whether a proxy is supported, and the exact connection format to test.”
Also ask whether the change affects existing customers, whether there is an additional fee, and what address remains available for rollback. If the supplier cannot confirm custom-hostname support, retain the supplied service address. Do not point a domain at a hostname copied from an unrelated reseller.
Cloudflare’s DNS documentation describes a CNAME as a mapping from one domain name to another. For example, a provider-approved record might use service.example.com as its name and approved-target.example.net as its target. Both are illustrative placeholders, not Lion service addresses.
The CNAME target is a hostname. Do not enter https://, a port, a playlist path, a username or a password in that field. The application URL is configured separately. Record the existing DNS settings before making an approved change, and leave unrelated website and email records untouched.
Ask the supplier whether the destination application also needs to recognize your hostname. DNS can reach a server even when that server has not been configured to serve your custom address.
For a direct HTTPS connection, the certificate presented to the client needs to be trusted and valid for the hostname being used. A DNS alias is not a certificate. Cloudflare’s Full (strict) documentation similarly sets explicit certificate requirements for its connection to an origin.
A separate detail matters if a supplier mentions a Cloudflare Origin CA certificate: Cloudflare explains that these certificates are for the Cloudflare-to-origin connection and may be untrusted by clients connecting directly. Ask whoever manages the service to provide the appropriate certificate arrangement.
If a certificate warning appears, stop the migration and have the supplier correct the hostname or certificate configuration. Do not instruct customers to ignore warnings or disable certificate checks.
Cloudflare documents proxy limitations for protocols, ports and some CNAME targets. Turning on a proxy changes the connection path; it is not simply a cosmetic DNS setting.
Follow a setup explicitly supported by both your supplier and the infrastructure service. Confirm protocol and port compatibility before enabling a proxy. Do not treat a forum comment saying “it should work” as a deployment plan, and do not use a proxy toggle to work around a certificate error.
If only the custom address fails, send the supplier the hostname, error text, time zone, app version and baseline result. Keep credentials private. The reseller security checklist explains what to redact in support records.
Does a CNAME hide the upstream supplier?
Do not promise that. It is a DNS alias, not a guarantee of anonymity or private infrastructure.
Can I use the same URL on every device?
Only if the supplier confirms those clients and connection formats are supported. A portal field and an M3U field may expect different input.
Will a custom domain fix buffering?
It is not a general buffering remedy. Establish a working baseline and troubleshoot playback separately.
Before ordering, review the Lion OTT supplier and reseller panel page and confirm the options available for your specific account.
Research reviewed 8 October 2026. Reddit links document user questions and individual experiences; they are not official specifications or live outage reports. Product options depend on your supplier and account.
We use essential cookies to keep this website working. With your consent, we also use analytics cookies to understand website usage and improve our services. You can accept, reject or customize your choices at any time.