Create DNS records for Office 365 using Windows-based DNS
Create DNS records for Office 365 using Windows-based DNS
Contributors: 
Check the Domains FAQ if you don't find what you're looking for.
 |
Want some help?
|
If you host your own DNS records using Windows-based DNS, follow the steps in this article to set up your records for email, Skype for Business Online, and so on.
To get started, you need to find the DNS records for your domain in Windows-based DNS so you can update them. Also, if you're planning to synchronize your on-premises Active Directory with Office 365, make sure you don't need to first update your user principal name (UPN).
These are the main records to add. (Need more help? Get support.)
If you haven't yet verified your domain, you'll also need to add a record to do that:
If you have a SharePoint Online Public Website, you can set it up to use your custom domain.
Note: Typically it takes about 15 minutes for DNS changes to take effect. However, it can occasionally take longer for a change you've made to update across the Internet's DNS system. If you’re having trouble with mail flow or other issues after adding DNS records, see Troubleshoot issues after changing your domain name or DNS records.
Find your DNS records in Windows-based DNS
Task
|
Go to the page that has the DNS records for your domain.
You’re now ready to create the DNS records.
|
Add MX record
Add an MX record so email for your domain will come to Office 365.
Task
|
The MX record you'll add includes a value (the Points to address value) that looks something like this: <MX token>.mail.protection.outlook.com, where <MX token> is a value like MSxxxxxxx.
|
Remove any obsolete MX records.
If you have any old MX records for this domain that route email somewhere else:
|
Add CNAME records
Add the CNAME records that are required for Office 365. If additional CNAME records are listed in Office 365, add those following the same general steps shown here.
Important:
- If you have Mobile Device Management (MDM) for Office 365, then you must create two additional CNAME records. Follow the procedure that you used for the other four CNAME records, but supply the values from the following table.
- (If you do not have MDM, you can skip this step.)
Task
|
Add the email (Exchange) Autodiscover CNAME record.
|
Add the SIP CNAME record.
|
Add the Skype for Business Online Autodiscover CNAME record.
|
Add the additional CNAME record that is required for Office 365.
|
Add two CNAME records for Mobile Device Management (MDM) for Office 365
Important:
- If you have Mobile Device Management (MDM) for Office 365, then you must create two additional CNAME records. Follow the procedure that you used for the other four CNAME records, but supply the values from the following table.
- (If you do not have MDM, you can skip this step.)
Task
|
Add the MDM Enterpriseregistration CNAME record.
|
Add the MDM Enterpriseenrollment CNAME record.
|
Add a TXT record for SPF to help prevent email spam
Important: You cannot have more than one TXT record for SPF for a domain. If your domain has more than one SPF record, you'll get email errors, as well as delivery and spam classification issues. If you already have an SPF record for your domain, don't create a new one for Office 365. Instead, add the required Office 365 values to the current record so that you have a single SPF record that includes both sets of values. Need examples? Check out these details and sample SPF records. To validate your SPF record, you can use one of these SPF validation tools.
Add the SPF TXT record for your domain to help prevent email spam.
Task
|
What you’ll see
|
You might already have other strings in the TXT value for this record (such as strings for marketing email), which is fine. Leave those strings in place and add this one, placing double-quotes around each string to separate them.
|
|
Add SRV records
Add the two SRV records that are required for Office 365.
Task
|
Add the SIP SRV record for Skype for Business Online web conferencing.
|
Add the SIP SRV record for Skype for Business Online federation.
|
Add a record to verify that you own the domain, if you haven’t already
Before you add the DNS records to set up your Office 365 services, Office 365 has to confirm that you own the domain you’re adding. To do this, you add a record, following the steps below.
Note: This record is used only to verify that you own your domain; it doesn’t affect anything else.
Task
|
Gather information from Office 365.
|
Add a TXT record.
|
Verify your domain in Office 365.
Important: Wait about 15 minutes before you do this, so the record you just created can update across the Internet.
Go back to Office 365 and follow the steps below to request a verification check. The check looks for the TXT record you added in the previous step. When it finds the correct TXT record, the domain is verified.
|
Note: Typically it takes about 15 minutes for DNS changes to take effect. However, it can occasionally take longer for a change you've made to update across the Internet's DNS system. If you’re having trouble with mail flow or other issues after adding DNS records, see Troubleshoot issues after changing your domain name or DNS records.
Non-routable email address used as a UPN in your on-prem Active Directory
If you're planning to synchronize your on-premises Active Directory with Office 365, you’ll want to make sure that the Active Directory user principal name (UPN) suffix is a valid domain suffix, and not an unsupported domain suffix such as @contoso.local. If you need to change your UPN suffix, we’ve got instructions to help you with that.
Note: Typically it takes about 15 minutes for DNS changes to take effect. However, it can occasionally take longer for a change you've made to update across the Internet's DNS system. If you’re having trouble with mail flow or other issues after adding DNS records, see Troubleshoot issues after changing your domain name or DNS records.
No comments:
Post a Comment