How to Add the SRV Records for Office 365 to a DNS Provider

The documentation provided with Office 365 combined with the new interface make configuration of it much simpler than with BPOS. However, it isn’t without a few small bumps. I ran into one of these when I was setting up our own organization to use the Lync features. One of the requirements was to add two SRV records to our external DNS, as per the image below:

image

There are actually some great guidelines and walkthroughs for setting this up with specific registrars, such as GoDaddy. However we’re using DynDNS, which is not one of the ones documented. Fair enough, I can find my way around a configuration screen, but the problem was that our DNS provider is somewhat old school. The SRV records are considered advanced (and therefore assume that I know what I’m doing with DNS), so instead of giving me nice, clearly defined fields like TTL, Port, and weight, I am presented with a single TXT field entry screen.

image

This is fine if you’re a DNS expert, and know how to construct the strings, but I’m not. After a fair bit of hunting around, I was able to sort out the following syntax for adding the requisite SRV records:

Host TTL Type Data
_sip._tls.mydomain.com 60 SRV 1 100 443 sipdir.online.lync.com.
_sipfederationtls._tcp.mydomain.com 60 SRV 1 100 5061 sipfed.online.lync.com.

 

Take special note of the period at the end of the data field – this is in fact required. Once these values were added, we were off to the races with Lync – which is awesome by the way…

Your mileage may vary depending on your DNS provider, but hopefully it will help if you’re in a similar situation.

Advertisements

26 thoughts on “How to Add the SRV Records for Office 365 to a DNS Provider”

  1. holy jesus christ ! i’m looking for 2 weeks for that informations ! you are such a great guy ! THANK YOU !!!

    DNS tools are so lame and theres no logic ! to put everything together in one field….makes no sense, but now, it does ! thank you.

    now, my DNS is working fine

  2. Good god thank you – I even use a DNS provider that allows me to add SRV records exactly as Office365 prescribes. However, it was your point about taking special note of the period at the end of the data field – when I added that to my target, it finally worked. Microsoft does not indicate that you need to add a period at all – but I tried it just based on your recommendation and it worked. Thanks so much!

  3. Unbelievable!! Thank you. I don’t care if “weight” and “priority” might be backwards. 365 accepted it. Change later if need be.

  4. Excellent. I was Scratching my head trying to get this working. My hosting company had Priority text box so I needed to remove that.

    Thanks

  5. Hello, My office 365 still wont verify the entries I created based on the information below. I was able to create the records on the dyndns page. I created two versions with ttl 3600 and 60

  6. Thanks, this was really helpful for me. I am using Hosting Controller .NET (aka iHostASP.NET’s new platform). I had to use a fully qualified hostname, like this:

    _sip._tls.mydomain.com. IN SRV 100 1 443 sipdir.online.lync.com.

    _sipfederationtls._tcp.mydomain.com. IN SRV 100 1 5061 sipfed.online.lync.com.

    *** also note that it took maybe 5 minutes before Office 365 recognised these changes, which confused me even more at the beginning. You really have to make a change, then wait a bit and be patient, otherwise you might fix it and then break it again without realising!

  7. The post is rather old but I was wondering if there is a good guide on editing the DNS on a C-Panel/WHM. I spent hours with an Office 365 tech support trying to figure out the problems with the entries, I mean, I don’t use some weired platform beside not using GoDaddy… Thanks all.

  8. You are a LEGEND!! I have been having all sorts of problems getting this working using Telstra CustData. Your DNS string info saved the day!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.