Use Your Own Domain for Videos and Channels

Use a dedicated hostname such as videos.example.com to present supported DynTube video and channel links under your brand. The Dashboard creates a pending domain record, shows the DNS target, verifies ownership, and provisions HTTPS before the hostname becomes active.

Before changing DNS

• Confirm the account plan includes custom video domains and your role can manage them.
• Choose a subdomain that is not already serving your website, email, or another application.
• Identify the DNS provider authoritative for the domain.
• Lower DNS TTL in advance only when your operational policy calls for it.

Add and configure the domain

Dashboard → Custom Domains

1. Choose Add Domain and enter the complete hostname without a URL path.
2. Save it and open DNS Setup for the pending record.
3. Copy the CNAME name and value shown by DynTube.
4. Create that CNAME at your DNS provider and remove any conflicting record for the same hostname.
5. Wait for DNS propagation, DynTube verification, and SSL provisioning.
6. Return to Custom Domains and confirm the status is Active.

The current Dashboard commonly instructs video domains to point to custom.dyntube.com, but copy the target displayed for your record because environment and platform configuration can evolve. DNS changes may take time according to resolver caches and the record TTL.

Use the active hostname

Generate or copy supported branded URLs after activation. Do not replace the host in an arbitrary legacy URL: current video, channel, iframe, and signed-link routes can have different shapes. Preserve query parameters and signatures exactly.

Verify DNS, TLS, and playback

• Public DNS resolves the hostname to the target DynTube provided.
• HTTPS presents a valid certificate for the custom hostname.
• A current branded video link and channel link load successfully.
• Embedded playback works from each approved production origin.
• Expired signed links and unauthorized viewers or origins are still denied as designed.

Troubleshooting

A pending domain usually means DNS has not propagated or the record does not match. A certificate issue should be investigated after DNS is correct. Capture the hostname, displayed target, record type, status, and time for support; do not send DNS account credentials or private signing keys.