Those entering the world of Microsoft UC solutions with Teams are not familiar with the following DNS entries. Those coming to Microsoft Teams from Lync or Skype for Business Server know them very well.
Am I interested in these entries as a TEAMS administrator? Absolutely!
- Missing DNS records can accidently prevent appreciated business relationships through Interop Federation between Microsoft Teams and Skype for Business.
- One or another Contact Center solution for Microsoft Teams still relies on Interop Federation between Microsoft Teams and Skype for Business for some features.
- Incorrect values can cause me headaches when integrating new domains into my tenant.
If I want to chat with a business partner still on Skype for Business Server, his Server infrastructure uses the SRV record sipfederationtls to my domain to find me as a Federated Partner. Target for this SRV record is the Skype for Business Online Access Edge Server sipfed.online.lync.com.
If my company only uses Microsoft Teams, the other entries are not relevant to me. Aren’t they?
Today Microsoft recommends ALL entries, and for good reason: For example in case of a company acquisition, where the information about an infrastructure and its history is incomplete, the Teams administrator can get lost when troubleshooting: Outdated DNS entries for decommissioned Lync or Skype for Business Servers always impact Teams services and Federation.