The only P2P eCDN compatible with mDNS for efficient live video streaming in all browsers
The importance of corporate webcasting increases every day. But the ongoing development of web applications continually creates new challenges for software providers, such as StriveCast, whose mission is to optimize webcasting. One of them is mDNS. Learn more about what mDNS is, why it can impede efficient corporate webcasting, and how StriveCast solves this problem as the only eCDN provider.
What is mDNS?
MDNS stands for Multicast Domain Name System and a security feature that has been rolled out by major browsers in the last years. It is used to resolve hostnames to IP addresses in local networks. In a nutshell, it prevents websites from collecting the device’s local IP address to use it for purposes like advertising or collecting network information. As the IP addresses are not retrievable, any external service or organization outside the internal network cannot draw any conclusion about the network’s structure and size. This security measurement protects against unauthorized access to device data but can also hinder some applications. MDNS can be activated in most major browsers and is applied as a security feature in most companies.
Why is mDNS a problem for corporate webcasting and how can it be solved?
To enable a smooth-running, high-quality video stream, most companies are using an eCDN. There are several ways an eCDN can optimize streaming within corporate networks, and a common one is creating a peer-to-peer network. Therefore, the P2P eCDN creates clusters of users who share the streamed content among themselves instead of downloading it individually from the origin server. By offloading the demands on the origin server, the stream becomes stable, and the video quality increases.
Most P2P-based eCDN providers struggle with mDNS-enabled networks, as the eCDN needs to use the IP addresses to form peering groups within an organization’s network. With mDNS, this becomes much harder to do. Therefore, most eCDN providers require their customers to install specific local 3rd-party software on every client-device (i.e., desktop or laptop). By installing this software, equipped with permissions to read and analyze the end device’s entire network traffic, the eCDN client can identify the device’s local IP address from the network interface. Although this setup works, it is very inconvenient as it requires organizations to roll-out and installs 3rd-party software on every single end device within the network. For many companies, this means a massive time commitment. Whenever possible, most companies avoid unnecessary, permanently installed software to keep workflows efficient and dynamic. Meanwhile, mDNS is already integrated and enabled in most browsers, so the mDNS challenge arises in many use cases of a P2P eCDN.
How StriveCast solves the problem with mDNS and peer-to-peer software
StriveCast has a different and more dynamic approach to solving the challenge of mDNS. Instead of placing local 3rd-party software on each end device, StriveCast makes use of its existing infrastructure. The StriveCast Network Manager is a server component contacted by all end devices using the company’s video platform. This already happens without the need for any local 3rd-party software, but through the pre-integrated web client of StriveCast, packed right in the existing video platform. By placing this server component inside the corporate network, it can see all IP addresses within the system, solving the mDNS problem centrally.
Therefore, StriveCast only requires you to do only a single change instead of changing every single end device. Also, StriveCast does not introduce any new 3rd-party software but uses what’s already in place. All in all, it shortens deployment times, cuts maintenance costs, and ensures no additional risks on end devices.