SRV records for Lync
-
Hi,
I have added 2 x SRV records for Lync online on the domain northantssar.org but when I test using nslookup they are not visible.They should look like this:
SRV _sip _tls 443 1 100 1 hour northantssar.org sipdir.online.lync.com
SRV _sipfederationtls _tcp 5061 1 100 1 hour northantssar.org sipfed.online.lync.comDo you know why they cannot be resolved with nslookup?
The blog I need help with is: (visible only to logged in users)
-
Hi,
Is there any actual support here or is it just post on a forum and hope to get lucky? -
I’ve just checked using nslookup and
- my SRV records do not show up
.
Please can someone help me with this to enable Office365 to work on this domain.
-
Zero response from any WordPress engineers on this topic, guess we are paying the price for a free WordPress account (AKA zero support).
Would appreciate an answer from a WordPress DNS engineer please.
-
So the first thing I notice is that you have both MX and TXT records. Which is something that this document says not to do:
Also, have you seen this document:
-
My question is why do my SRV records not show up in NSLOOKUP
All the records I have I was asked to put there by Microsoft and Microsoft engineers have examined them.
So, the original question still stands…why are my SRV records not visible?
These are required for Lync Federation, your DNS editor allows them to be created but they cannot be resolved.
-
I’m not having trouble seeing those records. Screenshot:
A question, are you looking for causes because something isn’t working? Or are you just curious about the visibility of the records?
-
Hello and thank you for looking into this request.
If you use NSLOOKUP the SRV records are not visible/do not resolve
Microsoft use automated NSLOOKUP tools to test for existence of all DNS records on Office365 platform.
Their tools cannot see the SRV so this breaks:
Lync Federation
Lync Desktop Client autodiscover
Lync IM
Adding External Users to Lync Contacts
Contacting External Organisations
Prevents contacting ‘domestic’ Skype users being contactedUsing Lync between members on our own domain is fine because on same domain it uses CNAME sip.northantssar.org instead of SRV
So, why are SRV records visible using DIG but not NSLOOKUP please?
-
So, why are SRV records visible using DIG but not NSLOOKUP please?
I am unsure and find that confusing as well.
One thing that I noticed is that there appears to be an extra underscore in the SRV record, “__sipfederationtls” instead of “_sipfederationtls”
I have switched that to the single underscore. Let’s see if that helps.
-
Hi,
Thanks but that does not make any difference.See the screenshot here >> http://www.goatsurfer.com/images/tech/SRV_records_error.png
The issue is them not being visible by NSLOOKUP and I would hazard a guess its the way WordPress creates/formats the records.
It looks like this:
Service __sipfederationtls (TCP) Priority 100 Weight 1 Target Host sipfed.online.lync.com:5061
When it should look like this:
_sipfederationtls _tcp 5061 1 100 @ sipfed.online.lync.com
-
Okay, it looks like there was a bug in there adding a second underscore. The records should now be saved without the second underscore. Once propagated, NSLOOKUP should show them.
-
staff-ozmodiar
Your fix worked !!
I am so pleased – Thank you for your help and apologies for my impatience at the start of this incident
- The topic ‘SRV records for Lync’ is closed to new replies.
WordPress.com Forums 
