When you try to verify a domain in Microsoft Office 365, you experience one or more of the following symptoms.
- When you try to verify a domain through the Office 365 portal, you receive the following error message:
Sorry, we can't find the record you created.
- When you try to verify a domain by using Windows PowerShell, you receive the following error message:
Confirm-MsolDomain : Domain verification failed. The requested CNAME record was not found. If you have recently updated your DNS settings for this domain, note that there may be a delay before this can be verified.
At line:1 char:1
+ Confirm-MsolDomain -DomainName rapaxonline2.com
+ CategoryInfo : OperationStopped: (:) [Confirm-MsolDomain], MicrosoftOnlineException
+ FullyQualifiedErrorId : Microsoft.Online.Administration.Automation.DomainVerificationMissingCnameException,Microsoft.Online.Administration.Automation.ConfirmDomain
This issue occurs if one of the following conditions is true:
- The Domain Name System (DNS) record isn't created correctly.
- The DNS record isn't propagated to all DNS servers. The changes to the Simple Mail Transfer Protocol (SMTP) domain may take 72 hours to propagate to all DNS servers.
To resolve this issue, check whether the DNS record exists for the domain. To do this, use one of the following methods, as appropriate for your situation:
Method 1: Use the Office 365 Health, Readiness, and Connectivity Checks to confirm that the correct DNS records are available
Administrators can use the Health, Readiness, and Connectivity Checks provided by Office 365 to validate their records are being correctly propagated. To do this, follow these steps:
- Browse to http://aka.ms/checkmypc
- Enter your Office 365 credentials, and then choose Quick Checks.
- Use the results to troubleshoot the issue.
Method 2: Use the Nslookup command-line tool
To check whether the DNS record exists by using the Nslookup command-line tool, follow these steps:
- Start Command Prompt.
- At a command prompt, type nslookup, and then press Enter.
- For TXT record, type Set type=txt, and then press Enter.
For MX record, type Set type=mx, and then press Enter.
- Type the domain name what you try to verify, and then press Enter.
- Note the output.
If you don't receive these results, the TXT record or MX record isn't entered correctly.
- For a TXT record, the output resembles the following:
treyresearch.net text =
- For a MX record, the output resembles the following:
contoso.org MX preference = 10, mail exchanger = ms27039633.msv1.invalid.outlook.com
Note If any changes occur to any DNS record, wait up to 72 hours for the changes to propagate before you try to verify the domain again.
The following example shows the commands and the data that are returned at a command prompt when you run Nslookup:
Default Server: dns1.corp.contoso.com
> server <IP_Address>
Default Server: [ <IP_Address> ]
> set type=txt
Server: [ <IP_Address> ]
contoso.com text =
If the domain still can't be verified, contact Office 365 Support.
For more information about how to troubleshoot domain verification issues in Office 365, see the following Microsoft Knowledge Base article:
Troubleshoot domain verification issues in Office 365
Still need help? Go to the Office 365 Community
Article ID: 2812447 - Last Review: July 7, 2014 - Revision: 6.0
|o365 o365a o365p o365e o365m o365022013 KB2812447|