Fix Microsoft 365 and Exchange Email Alias Delivery with DNS Records
Question details
Configure email delivery for aliases on a separate domain whose public DNS records do not provide a usable mail route.

- Product
- Microsoft 365 Exchange Online or on-premises Microsoft Exchange
- Device & OS
- not provided
- Scenario
- Senders need to deliver messages to email aliases that use a different domain from the primary email address.
- Observed behavior
- Messages to the aliases are rejected because public DNS lookups return no usable MX, A, or AAAA records for mail delivery.
Identify each affected alias domain and its DNS hosting provider, and confirm whether its mail is hosted in Microsoft 365 or on-premises Exchange. You will need access to the domain's public DNS settings and the appropriate mail administration center.
Configure DNS and accepted domains for email aliases
Use this solution when public DNS cannot route messages to the environment that hosts the aliases.
Run a public DNS lookup for each alias domain, such as `nslookup -type=mx example.com`. If no MX record exists, check the domain's A and AAAA records as well; mail servers may use those addresses as a fallback when there is no MX record.
Open the alias domain's public DNS settings at its DNS provider and add or correct the MX record for the mail environment that receives its messages. For Microsoft 365, check the required record under Microsoft 365 admin center > Settings > Domains; for on-premises Exchange, use the mail gateway hostname supplied by your administrator. Confirm that the MX target resolves to a reachable IP address.
In the Exchange admin center, open Mail flow > Accepted domains and confirm that each alias domain is listed and configured for your mail-routing setup. Add the domain if necessary; in Microsoft 365, complete any required domain ownership verification in Settings > Domains.
In the Exchange admin center, open Recipients > Mailboxes, select the intended mailbox, and check its email addresses. Add or correct the alias if it is missing.
After DNS changes have had time to propagate, repeat the public MX lookup and send a test message to an affected alias from an external account. If delivery still fails, review the new rejection message for the next issue.

Work with Office files in WPS Office
WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations in a familiar interface. Its support for Microsoft Office formats helps you move existing files into your workflow. Email alias routing must still be fixed in your DNS and mail administration settings.

Frequently Asked Questions
Does every alias domain need its own MX record?
Each alias domain needs a usable public mail route. An MX record normally directs mail to the correct environment; if no MX record exists, sending servers may fall back to the domain's A or AAAA record.
Where can I find the Microsoft 365 MX record for my domain?
In the Microsoft 365 admin center, go to Settings > Domains, select the domain, and review its DNS records. Publish the indicated MX value at the domain's public DNS provider.
Why is my alias still rejected after I add the MX record?
DNS changes may still be propagating, or the domain may not be configured as an accepted domain. Check Mail flow > Accepted domains in the Exchange admin center, then check Recipients > Mailboxes to confirm that the alias is assigned to the intended mailbox.
Can WPS Office fix the email alias DNS error?
No. The mail route must be corrected at the public DNS provider and, where needed, in Microsoft 365 or Exchange. WPS Office can be used to document the configuration but does not manage Exchange mail routing.




