Outlook Web App > For Exchange Online Administrators > Configure Your Domain for Live@edu > Configure DNS for Live@edu >

Create DNS Records for Live@edu

Applies to: Live@edu

Topic Last Modified: 2011-11-22

To get your domain up and running, you need to create or modify some or all of these DNS records at your DNS hosting service:

Your DNS hosting service may not support all these DNS record types, but they should support MX records and CNAME records. Need instructions for specific DNS hosting services?

Don't know who your DNS hosting service is? See Domain Name Registration and DNS Hosting Services.

Before you begin

The Live@edu Service Management Portal provides the information you need to create each type of DNS record. The values for several types of records include a unique 30-character token for each domain. When you create the DNS records, to avoid typos, copy and paste the information from the Service Management Portal to the data entry form for your DNS hosting service.

Typically, DNS records that you create for new domains are detected quickly. Updates to DNS records for existing domains may take longer to be detected. However, it should take no longer than 72 hours before a change is detected.

Most DNS hosting services let you modify your own DNS records. Typically, you log on to a Web interface with the logon name and password provided by your DNS hosting service. If your DNS hosting service doesn't let you modify your DNS records directly, they typically ask you to send requests so that they can make the changes for you.

DNS record to verify that you own the domain

Important   You only need to create one record to prove domain ownership.

You’ll need the unique token for your domain. The token is displayed in the Service Management Portal when you are asked to prove domain ownership. In the examples below, replace <token> with the exact value from the Service Management Portal, such as 418dfb2662004683978f9ce4742099.

You'll need the following information:

TXT record

  • Value   v=msv1 t=<token>

MX record

  • Target or Destination or Mail Server   <token>.msv1.invalid
  • Priority   100 or Low.
    Important   To prevent a conflict with the MX record that routes e-mail to your domain, pay close attention to the Priority value. A lower value indicates a higher priority. For example, a record with a Priority of 10 is processed before a record with Priority of 100. The MX record for mail routing should use a low number like 10, and the MX record for proving domain ownership should use a high number like 100.

After you create the DNS record to prove domain ownership, return to the Service Management Portal to check the status of your service.

Top of page

MX record to direct e-mail to your domain

You'll need the following information:

  • Target or Destination or Mail Server   <token>.mail.outlook.com
    Enter the value of MX server, displayed under Update an MX record in the Recommended DNS updates section of the Domains page in the Service Management Portal.
  • Priority   10 or High

Important   If you have obsolete MX records for this domain that routed e-mail to another location, delete them.

Top of page

Autodiscover CNAME record to enable Outlook

You'll need the following information:

  • Alias   autodiscover
  • Target or Destination   autodiscover.outlook.com

After you've created the autodiscover CNAME record and created user accounts, you can point your users to Connect Outlook to This Account to help them create a new Outlook profile and connect.

Top of page

SPF record to validate e-mail sent from your domain

You'll need the following information:

  • Value   v=spf1 include:outlook.com include:spf.messaging.microsoft.com ~all

Top of page

SRV record to enable instant messaging clients

You'll need the following information:

  • Service   _sipfederationtls
  • Protocol   _tcp
  • Priority   10
  • Weight   2
  • Port   5061
  • Target   federation.messenger.msn.com

Top of page