What is White-Label DNS Rebranding?
Protocol Definition & Architecture: Reseller Configuration
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.
Reseller Panel Configuration
Resellers should verify White-Label DNS Rebranding on every new line with a 24-hour trial before invoicing. Document the expected values in your onboarding message so customers can self-serve, and escalate to the provider desk with a Wireshark capture when behaviour deviates.
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 are reseller credits priced and how is the margin calculated?
Credits are bought in tiers: $3.00 each at 50 credits, $2.20 at 100, $1.80 at 250, and $1.40 at 500+. One credit creates a 1-month line that retails for $10-$15. At the Pro tier (100 credits for $220) sold at $12/month, gross revenue is $1,200 and net profit is $980, a 445% return on the credit purchase.
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.
What is device MAC address binding and why does my MAG box or Smart TV app ask for it?
Stalker / Ministra middleware authenticates a set-top box by its 48-bit MAC address (MAG boxes use the 00:1A:79 OUI prefix) instead of a username and password. The reseller panel binds that MAC to a subscription line; apps such as IBO Player and Smarters on Samsung or LG TVs generate a virtual MAC that must be registered the same way. If you replace the device, the panel must re-bind the new MAC or the portal returns an "unregistered device" error.
Do providers offer a free trial and how long does activation take?
Every network in this directory issues 24-hour trial lines from the reseller panel. Activation is instant: the panel writes the line to the Xtream database and the player can authenticate within 10 seconds. Trial lines are usually limited to 1 connection and exclude PPV bouquets.
What is the difference between Xtream Codes API, M3U URL, and Stalker Portal login?
All three deliver the same channels. Xtream Codes API uses player_api.php JSON endpoints so the player lazy-loads categories and EPG in seconds. An M3U URL (get.php) downloads a single text playlist of every stream, which is slow with 45,000 channels but works on any player. Stalker Portal authenticates by MAC address through a /c/ portal URL and is used by MAG receivers and some Smart TV apps.
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.