mx record

2 Topics

Unexpected Email Routing to Lower-Priority MX Record
We currently have two MX records configured in our public DNS: Primary MX Record: Priority 10 (EOP) Secondary MX Record: Priority 50 (retained temporarily) Despite the lower priority (higher numerical value) of the secondary MX record, we’ve observed instances of email traffic being routed to the priority 50 record. Could you help clarify why this might occur? Specifically: Are there scenarios where a higher-priority MX record (10) might be bypassed in favor of a lower-priority record (50)? Could this indicate misconfiguration, DNS propagation delays, or server availability issues? We aim to ensure proper email delivery to the intended priority 10 endpoint and would appreciate guidance on resolving this discrepancy.
Solved
Salamat_Shah
Apr 13, 2025 Place Exchange
143Views
0likes
2Comments
Issue with DnsConnectorDelivery
Background: We are currently migrating from Exchange 2016 to 2019 in a hybrid environment. We have 2 2016 servers both in our main datacenter, and 2 2019 servers, one in our main datacenter and one in our offsite datacenter. Backup datacenter has its own DCs that are replicas of our main datacenter's DCs. Exchange 2019 has been installed and updated to CU 11. Problem: When I run the hybrid configuration wizard and select all 4 servers to be included in the send and receive connectors, everything completes and no errors appear. However, mail gets stuck in the DnsConnectorDelivery queue on the server in our backup datacenter. The NextHopDomain for the stuck mail is our M365 domain, domain.mail.onmicrosoft.com As soon as I remove the server in the backup site from the send and receive connectors, mail flows correctly again. I've done a lot of internet searching and it seems the issue has something to do with our MX record, but both domains have the correct record in their DNS. What could be causing the issue? Any help is appreciated!
ltd224
Jun 08, 2022 Place Exchange
2.8KViews
0likes
0Comments