Let’s now check the meeting functionality. I can indeed start a meeting from “Meet Now” menu…
But when we reveal the Meeting Join Information, our URL points to meet.drago.ws and not drago.local and… internal users cannot connect to a meeting.
Quick look in our certificate shows that because of our entries in Topology Builder, meet.drago.ws and dialin.drago.ws is included in the list or SAN (Subject Alternative Name)
...and so, all we need is to create the appropriate A-records in our drago.ws internal zone.
Once again – rejoice! Internal users now join the meeting as expected.