Wildcard Certificates cause MS Teams Connectivity Test to fail
Closed this issue · 1 comments
The MS Teams Connectivity Test throws Errno -9] Address family for hostname not supported (pictured below) when properly configured with a working (both inbound and outbound) setup for Direct Routing.
I think this relates to #271. The hostname check is also failing, and for the TLS Certificates check it is likely failing around here since the TLS library is not handling the wildcard (eg: *.sbc.example.com) well and likely needs to be directed to the particular domain we are checking? (If I am reading this code right...)
Operating System: Debian 10.9 (64-bit)
dSIPRouter Version: Master (installed 3 days ago with -all flag)
Note: Opening this issue at @mackhendricks request based on our conversation on Friday, June 11th 2021.
I can't reproduce this issue. I was able to successfully execute the connectivity test with a wildcard cert of *.customers.dsiprouter.net. As shown below.
