The global push and playback scheduling of LVB is based on the DNS of the domain name by default, which is the most common and simplest access method. Due to the complexity of global network environments, domain name resolution errors or cross-network traffic occur frequently. It is recommended that you use the HttpDNS solution to optimize global live broadcasting scheduling.
An ISP's LocalDNS egress performs NAT based on an authoritative DNS destination IP address or forwards the resolving request to other DNS servers, making it impossible for the authoritative DNS to correctly identify the ISP's LocalDNS IP and thus causing domain name resolution errors and cross-network traffic.
Empowered by world-leading DNS cluster technology, Tencent Cloud HttpDNS supports multiple ISPs and custom lines for optimal scheduling. For more information, see [HttpDNS].
This document uses the free edition of HttpDNS as an example to describe how to use the HttpDNS scheduling solution for Tencent Cloud Global LVB. For APIs of the free edition, see the related [documentation].
http://18.104.22.168/d?dn=$push_domain.&ip=$ip, which is an HTTP Get request. The meanings of the parameters are as follows:
Here, server_ip is the IP obtained in Requesting the Upstream Access Point IP, and the spliced push URL is as follows:
rtmp://server_ip/live/streamname?txTime=xxx&txSecret=xxx&txHost=domain. The most important step is to add the txHost field representing the push domain name of the service to the original push parameters.
http://22.214.171.124/d?dn=$domain.&ip=$ip, which is an HTTP Get request. The meanings of the parameters are as follows:
http://server_ip/play_domain/live/streamname.flv?xxxxxxxxxx http://server_ip/play_domain/live/ streamname.m3u8?xxxxxxxxxx http://server_ip/play_domain/live/ streamname -123.ts?xxxxxxxxxx
https://play_domain/live/ streamname.flv?xxxxxxxxxx https://play_domain/live/ streamname.m3u8?xxxxxxxxxx https://play_domain/live/ streamname -123.ts?xxxxxxxxxx
The schemes above are all based on the global scheduling platform of LVB and should not be used for scheduling in Mainland China without necessary modifications.