Forum Discussion
Solved
Are the DNS records for Skype for Business Online still required when in Teams Only?
Can someone answer if I can delete the old DNS entries? Have been running Teams only mode since March 2020. We have a few users with the PSTN from Microsoft as Add-On. One license is for Polycom Tr...
- It does also say:
Note
These DNS records also apply to Teams, especially in a hybrid Teams and Skype for Business scenario, where certain federation issues could arise.
As I say, plenty of customers don't have them and never had a problem but others have when there's no SRV record. If you also have federated partners who use Skype for Business, then you'd need those records for them to federate with you.
I found those docs, And it clearly states for Skype for Business Online. I understand what you mean. I was just cleaning up and it seems strange to leave entries that reference Lync and Skype when those haven't been used for more than a year in our case. Even this doc has similarly obscure details
https://docs.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/create-dns-records-at-any-dns-hosting-provider?view=o365-worldwide
https://docs.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/create-dns-records-at-any-dns-hosting-provider?view=o365-worldwide
It does also say:
Note
These DNS records also apply to Teams, especially in a hybrid Teams and Skype for Business scenario, where certain federation issues could arise.
As I say, plenty of customers don't have them and never had a problem but others have when there's no SRV record. If you also have federated partners who use Skype for Business, then you'd need those records for them to federate with you.
Note
These DNS records also apply to Teams, especially in a hybrid Teams and Skype for Business scenario, where certain federation issues could arise.
As I say, plenty of customers don't have them and never had a problem but others have when there's no SRV record. If you also have federated partners who use Skype for Business, then you'd need those records for them to federate with you.
- Is this still true?
`sipdir.online.lync.com` and `webdir.online.lync.com` are no longer resolving in dns, so i removed the `CNAME` and `SRV` entries pointing to them.- I have the same question.
Whilst trying to update some other DNS records, my control panel is refusing to let me commit changes as these errors are now showing as faulty due to not resolving to A, AAAA or CNAMEAccording to this article now, scroll down to the "External DNS records required for Teams" section, it now says that only the SRV _sipfederationtls._tcp record is needed. It points to sipfed.online.lync.com and that DOES still resolve.
https://learn.microsoft.com/en-us/microsoft-365/enterprise/external-domain-name-system-records
This article also seems to indicate to delete the CNAME sip and lyncdiscover records and _sip._tls SRV record, and leave only the _sipfederationtls._tcp SRV record.
https://learn.microsoft.com/en-us/SkypeForBusiness/hybrid/decommission-manage-dns-entries
