{"id":24834,"date":"2015-10-12T20:24:59","date_gmt":"2015-10-12T18:24:59","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=24834"},"modified":"2019-02-25T11:58:30","modified_gmt":"2019-02-25T09:58:30","slug":"office-365-lync-online-srv-dns-records-on-amazon-route-53","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2015\/10\/12\/office-365-lync-online-srv-dns-records-on-amazon-route-53\/","title":{"rendered":"Office 365 Lync Online SRV DNS records on Amazon Route 53"},"content":{"rendered":"\n

One of the very few things we still rely on from Microsoft at work is Office 365<\/a>.  Not because it is so great, but because I simply didn’t have the time to move away yet (quiet Christmas season is coming soon).  Most people don’t get exposed much to it anyway, using Evolution or Thunderbird email clients, or forwarding everything to Gmail altogether.  But as an administrator of the service I get constantly annoyed by the “there are problems with your domain” notification.  After ignoring it for about a year, I decided to finally fix it.  All that was needed is a couple of records in the DNS zone.<\/p>\n

Unfortunately, the instructions Microsoft provides don’t quite well apply to Amazon Route 53<\/a> user interface.  It took me a few tries and some searching to find the right ones.  Here they are, thanks to a comment on this page<\/a>:<\/p>\n

First record:<\/strong><\/p>\n

1. Log into Route 53.
\n2. in the hosted zones window, check the box next to YOURDOMAIN.com
\n3. click  [ > Go to Record Sets]
\n4. Click  [Create Record Set]
\n5. Enter  _sipfederationtls._tcp , in the Name field
\n6. Switch type to SRV – Service locator
\n7. In the Value window Enter: 100 1 5061 sipfed.online.lync.com
\n8. Click [Create]<\/p>\n

Second record:<\/strong><\/p>\n

9. Click  [Create Record Set]
\n10. Enter: _sip._tls , in the name field
\n11. Switch type to SRV – Service locator
\n12. In the Value window Enter: 100 1 443 sipdir.online.lync.com
\n13. Click [Create]<\/p><\/blockquote>\n\n","protected":false},"excerpt":{"rendered":"\n

One of the very few things we still rely on from Microsoft at work is Office 365.  Not because it is so great, but because I simply didn’t have the time to move away yet (quiet Christmas season is coming soon).  Most people don’t get exposed much to it anyway, using Evolution or Thunderbird email … Continue reading Office 365 Lync Online SRV DNS records on Amazon Route 53<\/span><\/a><\/p>\n\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"Office 365 Lync Online SRV DNS records on Amazon Route 53 #Microsoft #Office365 #Amazon #AWS #Route53 #DNS","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false,"_links_to":"","_links_to_target":""},"categories":[1,133,62],"tags":[3270,3311,2366,3381,2289],"keyring_services":[],"class_list":["post-24834","post","type-post","status-publish","format-standard","hentry","category-general","category-sysadmin","category-technology","tag-amazon-aws","tag-amazon-route53","tag-cloud-computing","tag-microsoft-office-365","tag-web-hosting"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t