What is White-Label DNS Rebranding?
Protocol Definition & Architecture: Performance Benchmarks
Technical Definition
White-labelling lets a reseller present the service under their own brand by pointing a custom hostname (CNAME) at the provider edge and distributing a branded player APK, so subscribers never see the upstream domain.
How It Operates Under the Hood
The reseller creates a DNS CNAME such as tv.mybrand.com → edge.provider.net and registers it in the panel so the TLS certificate (via SNI) and Xtream handshake accept the new host. Smarters-style apps support 1-click domain binding, and panels can compile APKs with the reseller logo and preset host.
Reference Benchmarks
Our benchmarks for White-Label DNS Rebranding were captured across six CDN points of presence with Wireshark packet analysis. The specification table above lists the governing parameters; expect edge latency between 11 ms (London) and 52 ms (Sydney) and zero continuity-counter errors on tier-1 networks.
Protocol Engineering Specifications
| Stream Engineering Metric | Reference Specification | Governing Standard |
|---|---|---|
| DNS record | CNAME to provider edge |
RFC 1034 |
| TLS | SNI-based certificate per custom host |
Let's Encrypt / ACME |
| APK branding | Logo, name, preset host |
Panel build service |
| Transport Container | MPEG-TS (188 bytes: 4 B header + 184 B payload, 0x47 sync) |
ISO/IEC 13818-1 |
| Manifest Specification | Extended M3U8 playlist / LL-HLS 0.5 s parts |
IETF RFC 8216 |
| Decoder Pipeline | Hardware MediaCodec HEVC Main 10 (ExoPlayer / Media3) |
Android Media3 |
Packet-Loss & Throttling Mitigation
Forward Error Correction (FEC)
Edge ingest nodes add XOR / Reed-Solomon parity packets (RFC 6363 FECFRAME) at a 1:10 ratio. A client can reconstruct a single lost 188-byte transport packet inside each 10-packet block without any retransmission round-trip, which is why peak-hour UDP loss of 0.5% produces zero visible artifacts.
TCP BBR Congestion Control
Origin and edge servers run Linux with net.ipv4.tcp_congestion_control=bbr. Unlike CUBIC, BBR models bottleneck bandwidth and round-trip propagation time instead of treating random loss as congestion, so an HLS session on a lossy Wi-Fi link keeps its 18.5 Mbps throughput rather than collapsing to half.
DNS over HTTPS via 1.1.1.1
Set the player device or router resolver to https://cloudflare-dns.com/dns-query (RFC 8484). ISP resolvers that return NXDOMAIN or poisoned A records for streaming hostnames are bypassed, and resolution latency typically drops below 15 ms.
Jitter Buffer & Dual-Ingest Failover
Players should hold 5,000 ms of media (TiviMate "Large" buffer). Upstream, every channel is ingested from two independent sources; a continuity-counter error rate above 0.1% on the primary flips the mux to the backup within one GOP (2 seconds).
White-Label DNS Rebranding FAQ
What is White-Label DNS Rebranding in simple terms?
White-labelling lets a reseller present the service under their own brand by pointing a custom hostname (CNAME) at the provider edge and distributing a branded player APK, so subscribers never see the upstream domain.
Does a custom DNS slow down streams?
No. The CNAME resolves once; stream traffic still flows directly to the edge IP.
How far behind live are IPTV sports streams and can latency be reduced?
Standard HLS with 4-second segments and a 3-segment player window sits 12-18 seconds behind the broadcast. Low-Latency HLS with 0.5-second partial segments brings glass-to-glass delay to about 3.8 seconds, and raw MPEG-TS over HTTP (.ts output format) is typically 5-7 seconds behind. Choose the .ts output format in your player for live sports and reserve .m3u8 for VOD and catch-up.
What buffer size should I set in TiviMate, Smarters, or XCIPTV for 4K sports?
Set the largest option (5,000 ms in TiviMate, "Large" in Smarters). Buffer time in seconds equals buffer bytes multiplied by 8, divided by the stream bitrate in Mbps: a 15 MB allocation on an 18.5 Mbps 4K feed yields 6.5 seconds of protection, which covers typical ISP shaping bursts of 2-4 seconds without a visible freeze.
How do I know if my ISP is throttling IPTV streams, and how do I stop it?
Run a speed test on the same device while a stream buffers. If raw throughput is above 25 Mbps but the player reports a bitrate below 8 Mbps, your ISP is applying traffic shaping to the stream flow, usually triggered by deep packet inspection of the TLS SNI or by sustained UDP/TCP flows to known hosting ASNs. Stop it by routing the player through a WireGuard tunnel (which hides destination and SNI inside ChaCha20-Poly1305 encryption), switching DNS to 1.1.1.1 over HTTPS, and keeping a 5,000 ms player buffer so short shaping bursts never reach the decoder.
WireGuard vs OpenVPN: which VPN protocol is better for 4K IPTV?
WireGuard. It runs in the Linux kernel, uses a 4,000-line codebase with ChaCha20-Poly1305 encryption, and adds roughly 1-3 ms of latency with 5-8% throughput overhead, so an 18.5 Mbps 4K stream passes untouched. OpenVPN in TCP mode suffers from TCP-over-TCP meltdown during packet loss and typically costs 20-35% throughput; use OpenVPN only in UDP mode with tls-crypt on networks that block UDP port 51820.
How does multi-screen concurrency work and what happens if I exceed max_connections?
The Xtream Codes player_api.php handshake returns max_connections and active_cons. Each live or VOD stream request opens one session counted against that limit; a second TV, phone, or multi-view tile is a second connection. When active_cons would exceed max_connections, the server answers the new stream request with HTTP 403 / 458 and the player shows "max connections reached". Resellers should sell lines with 2-5 connections for households and enable IP-lock only for single-device subscribers.
Every external citation on this page points to a primary source: telecommunications RFCs, ITU-T and ISO codec standards, manufacturer and developer documentation, national regulators, or official sports governing bodies. No commercial IPTV competitor is cited.