Office 365 DNS for Success

1,751 views

Published on

Office 365 - DNS for Success - a short and sweet overview of a technical topic.

by Robert Dick, Office 365 MVP and Senior Consultant with itgroove

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,751
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Office 365 DNS for Success

  1. 1. Welcome! Office 365 DNS for Success! Robert Dick, Office 365 MVP Senior Consultant, itgroove
  2. 2. Who am i?  30+ years in IT, more than half in Consulting  Microsoft Office 365 MVP (one of 4 in Canada)  MCP, MCTS, VMSP, VMTSP  SMB Team Lead, Senior Consultant with itgroove  Blogger: http://thebeagle.itgroove.net
  3. 3. Office 365 DNS for Success!
  4. 4. I hope this won’t be toooo dry and boring …
  5. 5. DNS: OK, what is it? The “dry” definition: DNS is an abbreviation for Domain Name System, a system for naming computers and network services that is organized into a hierarchy of domains. DNS naming is used in TCP/IP networks, such as the Internet, to locate computers and services through user-friendly names. DNS defined: Domain Name System(DNS) - TechNet technet.microsoft.com/en-us/library/cc787920(v=ws.10).aspx
  6. 6. A little more friendly …  “Yellow Pages”, “Phone Book” or 411 for the Internet!  Maps IP addresses to textual information that we mere humans can read and understand (and systems can use)  Multiple record types (types of text) to facilitate different tasks and functions  Some simple, some not so much …
  7. 7. Some Standard DNS Record Types  NS – Name Server resource record: points to the authoritative nameservers for your domain  A – Address resource record: maps address 199.27.180.172 to name www.itgroove.net (lookup is name)  PTR – Pointer resource record: reverse of A record, maps name to address (lookup is address)  CNAME – Canonical name resource record: maps one name to another  MX – Mail Exchange resource record: maps IP, name and “weighted preference” for your email server(s)  SPF – Sender Policy Framework record: positively identifies authorized email senders for your domain  SRV – Service Resource record: relatively new type of record that maps for specialized services (like Lync)
  8. 8. Where does your DNS live?  External DNS lives at your Domain Registrar or your designated DNS provider, this is what everyone on the Internet “sees” (Your external domain is .com, .net, .org …)  Internal DNS lives on your internal DNS servers – normally your Domain Controllers in the Windows world (Your internal domain could be .local or something different from your external)  Both need to reference all of the required DNS records in order for your Office 365 to function correctly on your internal network as well as on the Internet  This probably means you will need “split brain” DNS entries in your internal DNS system (your internal DNS has records for both your internal domain as well as your external domain)
  9. 9. What DNS is critical to your Office 365 migration?  Microsoft defines the following as fundamental to bringing your O365 tenancy online:  msoid CNAME record pointing to a specified Microsoft DNS record for authentication  @ or yourdomainname.com TXT record used to verify ownership of your domain  autodiscover CNAME record pointing to autodiscover.outlook.com  <Mxtoken>.mail.protection.outlook.com MX record that points to the O365 mail servers  v=spf1 include:spf.protection.outlook.com –all SPF record  _sipfederationtls, _sip SRV records required for Lync operation  sip, lyncdiscover CNAME records required for Lync operation
  10. 10. Some “real world” examples (register.com) CNAME examples: MX example: SRV examples:
  11. 11. What’s Easy? What’s Not??  CNAME, TXT, SPF and MX are all relatively easy records to create yourself  SRV records are more complex, vendor UI’s may not allow you to easily enter the required information, be prepared to make multiple tries  Some third party suppliers don’t have the backend to support the SRV records (some of the ISP’s are in this situation)  If you can’t make the changes easily yourself you should be looking at another DNS provider! Microsoft lists a number of providers that work well with O365. Previous example of register.com shows a “clean” SRV record entry.
  12. 12. DNS entries all made! Now what?  Use the “test” button inside O365 to test DNS entries.  If all good O365 will “light up” your tenancy and you are good to go!  If not all good, O365 will highlight the DNS entries that are problematic so you can go back for another kick at the can.  Go through the loop until you are all good and tenancy is live!
  13. 13. Questions?
  14. 14. Thank you! Email: rdick@itgroove.net Blog: thebeagle.itgroove.net Web Site: www.itgroove.net

×