Hi there,
All of the Internet traffic from my corporate LAN has to traverse a web proxy, including traffic to Teams. Our web proxies allow connections to all URLs listed in the “Office 365 URLs and IPs” website but we can't have IP addresses in the web proxy allowed ACL.
We have noticed that Teams P2P calls are intermittently failing and after investigation we have found that some of the IP addresses that Teams is trying to connect don't have a DNS PTR record.
The web proxy whitelist validation does a DNS lookup when the connection is made to an IP address and if it can resolve a name for the IP address, it will check if that name/URL is in the whitelist, therefore allowing the connection. If the IP address can’t be resolved to a name then the connection is blocked because the web proxy can't validate if that is in the allowed list or not ;)
Using the Teams Network Assessment Tool (https://docs.microsoft.com/en-us/microsoftteams/3-envision-evaluate-my-environment) I can see that TCP/HTTPs connection fails against 4 IP address ranges because those IPs don't have a PTR record - see details below, which is why Teams P2P calls are intermittently failing.
I’m fully aware that P2P calls should be using UDP traffic and I’m working with my network team to allow UDP traffic from all of the different subnets we have, but I’m also wondering what else might be intermittently failing given that Teams can’t successfully establish a TCP/HTTPs connection to those IP addresses? - See attached file for full result of the Connectivity Analyzer test
Is someone reading this message able to raise a request to have PTR records created for those IP ranges, so there is consistency on all addresses that are used by Teams, please?
Thank you,
Eduardo
13.107.64.2 world.tr.teams.microsoft.com
13.107.65.5 eu.tr.teams.microsoft.com
52.113.192.2 world52.tr.teams.microsoft.com
52.113.193.5 eu52.tr.teams.microsoft.com
52.114.220.1 52-114-220-1.relay.teams.microsoft.com
52.114.220.254 52-114-220-254.relay.teams.microsoft.com
52.114.221.1 52-114-221-1.relay.teams.microsoft.com
52.114.221.254 52-114-221-254.relay.teams.microsoft.com
52.114.222.1 52-114-222-1.relay.teams.microsoft.com
52.114.222.254 52-114-222-254.relay.teams.microsoft.com
52.114.223.1 52-114-223-1.relay.teams.microsoft.com
52.114.223.254 52-114-223-254.relay.teams.microsoft.com
52.114.124.1 52-114-124-1.relay.teams.microsoft.com
52.114.124.254 52-114-124-254.relay.teams.microsoft.com
52.114.125.1 52-114-125-1.relay.teams.microsoft.com
52.114.125.254 52-114-125-254.relay.teams.microsoft.com
52.114.126.1 52-114-126-1.relay.teams.microsoft.com
52.114.126.254 52-114-126-254.relay.teams.microsoft.com
52.114.127.1 52-114-127-1.relay.teams.microsoft.com
52.114.127.254 52-114-127-254.relay.teams.microsoft.com
52.114.62.1 52-114-62-1.relay.teams.microsoft.com
52.114.62.254 52-114-62-254.relay.teams.microsoft.com
52.114.63.1 52-114-63-1.relay.teams.microsoft.com
52.114.63.254 52-114-63-254.relay.teams.microsoft.com
52.114.188.1 PTR doesn't exist
52.114.188.254 PTR doesn't exist
52.114.189.1 PTR doesn't exist
52.114.189.254 PTR doesn't exist
52.114.190.1 PTR doesn't exist
52.114.190.254 PTR doesn't exist
52.114.191.1 PTR doesn't exist
52.114.191.254 PTR doesn't exist
