You can't send email messages in Microsoft 365 from a domain that's set up for full redelegation
Problem
When you try to send email messages in Microsoft 365 for business from a domain that's set up for full redelegation, some messages aren't sent. Additionally, you may receive a nondelivery report (NDR) that resembles the following:
"smtp; 550 SPF MAIL FROM check failed (PermError)"
Note
A domain that is set up for full redelegation is a domain in which the name server (NS) resource records point to Microsoft 365. Full domain redelegation is available only for Microsoft 365 for business subscriptions.
Solution
To fix this issue, follow these steps:
Use the NsLookup tool to check whether the NS resource records point to Microsoft 365. To do this, follow these steps:
- Click Start, and then, in the search box, type command prompt.
- In the list of results, right-click Command Prompt, and then click Run as administrator.
- At the command prompt, type nslookup, and then press Enter.
- Type set type=ns, and then press Enter.
- Type your domain name (for example, type contoso.com), and then press Enter.
The NS resource records should point to two of the following:
- ns1.bdm.microsoftonline.com
- ns2.bdm.microsoftonline.com
- ns3.bdm.microsoftonline.com
- ns4.bdm.microsoftonline.com
If the domain was recently set up for full domain redelegation, wait 72 hours.
Use the NsLookup tool to perform a DNS lookup on the TXT (SPF) record. To do this, follow these steps:
- Click Start, and then, in the search box, type command prompt.
- In the list of results, right-click Command Prompt, and then click Run as administrator.
- At the command prompt, type nslookup, and then press Enter.
- Type set type=txt, and then press Enter.
- Type your domain name (for example, type contoso.com), and then press Enter.
The TXT (SPF) record should resemble the following:
"v=spf1 include:outlook.com ~all"
More information
For more information about the NsLookup tool, see NsLookup.
Still need help? Go to Microsoft Community.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for