Prove Domain Ownership for Live@edu

  • Article

Applies to: Live@edu

To confirm that you own the domain you are modifying, you create a record at your DNS hosting provider. When this DNS record is verified, your ownership of the domain is confirmed. Until the new DNS record is detected, the Service Management Portal will display the message asking you to confirm domain ownership. To check if the DNS record has been detected, click Refresh.

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.

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

Use a TXT record to prove that you own the domain

To use a TXT record to prove domain ownership, the TXT record must be in the exact format displayed when you are asked to prove ownership. For example, if your domain is contoso.edu, and the token is 0cbc8689f5394f86bc7b84983e30d3, then specify the following:

  • Host   contoso.edu
  • Value   v=msv1 t=0cbc8689f5394f86bc7b84983e30d3

Use an MX record to prove that you own the domain

The MX record used to prove domain ownership is a separate record from the MX record that you use for mail routing, and it points to an invalid MX server name that can’t be used for mail routing. To set up mail routing using an MX record, you need to create a separate MX record.

Important

To prevent a conflict with the MX record used for mail routing, pay close attention to the Priority or Preference value. The MX record used to prove domain ownership should have a lower priority than the mail routing MX record. Some domain hosting services use numbers to set priority, and some use High, Medium, and Low.

  • For hosting services that use numbers to set priority, note that a higher value implies lower priority. For example, if the mail routing MX record has a Priority of 10, you could use 100 for the MX record used to prove domain ownership.
  • For hosting services that use High, Medium, and Low to set priority, use Low for the MX record used to prove domain ownership, and Medium or High for the mail routing MX record.

The MX record used to prove domain ownership must be in the exact format displayed when you are asked to prove ownership. For example, if your token is 0cbc8689f5394f86bc7b84983e30d3, specify the following:

  • Target or Destination or Mail Server   0cbc8689f5394f86bc7b84983e30d3.msv1.invalid
  • Priority   100 or Low