{"id":535,"date":"2011-06-27T15:22:01","date_gmt":"2011-06-27T22:22:01","guid":{"rendered":"http:\/\/jim-zimmerman.com\/?p=535"},"modified":"2012-01-10T15:43:41","modified_gmt":"2012-01-10T22:43:41","slug":"linux-dns-and-office365","status":"publish","type":"post","link":"https:\/\/jim-zimmerman.com\/?p=535","title":{"rendered":"linux DNS and Office365"},"content":{"rendered":"

I have spending quite a bit of time recently playing with Microsoft’s Office365. I have been interested in how to manage the DNS records in my linux DNS to support Office365. For example, I wanted to access my Office365 email, Lync server, and Sharepoint via my specified hostnames as defined in my DNS. Email was simple enough. Setting up these records got the email to my domain directed properly, and I was able to use auto discover to configure my iPhone, android device and desktop computer email clients easily. I have listed the key records below:<\/p>\n

mydomain.com. 360 IN TXT “v=spf1 include:outlook.com ~all”<\/p>\n

$ORIGIN mydomain.com.
\n@ IN MX 0 mydomain-com.mail.eo.outlook.com.
\nms49911282 IN CNAME ps.microsoftonline.com.
\nautodiscover IN CNAME autodiscover.outlook.com.<\/p>\n

Lync presented a bit more of challenge. And I found several sources on the Internet of people trying to get the records set up properly, but all of them seemed to have something wrong. Ultimately, these are the records that I had to add to access my Office365 Lync server. The lesson learned from setting these records should help records that Active Directory requires that I have never had occasion to look at before.<\/p>\n

_sip._tls IN SRV 100 1 443 sipdir.online.lync.com.
\n_sipfederationtls._tcp IN SRV 100 1 5061 sipfed.online.lync.com.<\/p>\n

Sharepoint is giving me a bit of an issue that I have been trying to address with Microsoft, but they have been less than responsive. I hope this is not how small businesses can expect to be treated by Microsoft when this product goes live. It would certainly cause me to reconsider what I otherwise think is a pretty good product. Anyway, I believe I have the records defined properly, but I cannot verify them because I am unable to enable Sharepoint Online in my domain properties or intent ( I have added a screen shot of the issue at the bottom of this post.). <\/p>\n

My company records (Sharepoint site):
\nsharepoint IN CNAME mycompany.sharepoint.com.
\nsp IN CNAME mycompany.sharepoint.com.<\/p>\n

My public records (public Sharepoint site):
\nsharepoint-pub IN CNAME ProdNet11.SharePointOnline.com.
\nsp-pub IN CNAME ProdNet11.SharePointOnline.com.<\/p>\n

I will update this when, I finally hear something from Microsoft.<\/p>\n

\"Unable<\/a><\/p>\n

Here are the DNS settings as documented in Office365 for mydomain.com. This is the information Microsoft provides to help you add the appropriate records:<\/p>\n

\"Office365<\/a><\/p>\n

Update 1\/10\/2012:
\nWhile trying out the Lync client on my iPhone, I discovered that I was missing another DNS record to support Lync server auto-discovery. I just needed to add the following record to my DNS:<\/p>\n

lyncdiscover IN CNAME webdir.online.lync.com.<\/p>\n

This allowed iPhone Lync clients to use the auto detect server feature. I suspect that this was needed for other clients too, since I had to set it up manually before. I am going to try this on MacOS later to see if that works better too.<\/p>\n","protected":false},"excerpt":{"rendered":"

I have spending quite a bit of time recently playing with Microsoft’s Office365. I have been interested in how to manage the DNS records in my linux DNS to support Office365. For example, I wanted to access my Office365 email, Lync server, and Sharepoint via my specified hostnames as defined in my DNS. Email was [&hellip<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[82,164,48,187],"class_list":["post-535","post","type-post","status-publish","format-standard","hentry","category-documentation","tag-active-directory","tag-dns","tag-linux","tag-office365"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/535","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=535"}],"version-history":[{"count":4,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/535\/revisions"}],"predecessor-version":[{"id":538,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/535\/revisions\/538"}],"wp:attachment":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=535"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=535"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=535"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}