Google Meet Enterprise Content Delivery Network (Meet eCDN) uses the browser's JavaScript API to retrieve a device's private IP address and connect to peers on the local network. The private IP address of a device is usually hidden from the browser by mDNS, and connecting to peers requires local network access. To turn on Meet eCDN, you have to turn off mDNS and allow local network access.
Update the policies
mDNS and local network access are security measures. We recommend you control them on a per-domain basis. That way, you only expose IP addresses to Google and only allow Meet to access the local network. Both mDNS and local network access are controlled through Chrome policies.
To update the policies:
- Choose an option:
- If you manage Chrome through the Google Admin console and want to update the policies using the Admin console, follow the instructions at Set Chrome policies for users or browsers .
- If you manage Chrome using another system, follow the instructions at Set Chrome browser policies on managed PCs .
- Go to the WebRtcLocalIpsAllowedUrls policy and include meet.google.com in the policy to turn off mDNS.
- Go to the LocalNetworkAllowedForUrls policy and include meet.google.com in the policy to grant local network access.
Check policy status
To verify that the policies are correctly configured on a device:
- In the Chrome browser address bar, enter chrome://policy/.
- In the search bar, enter WebRtcLocalIpsAllowedUrls. The policy should include meet.google.com.
- In the search bar, enter LocalNetworkAllowedForUrls. The policy should include meet.google.com.