Some Microsoft outbound IPs in a set of DMARC reports appeared to have no PTR record. Could this affect deliverability under Spamhaus sender guidelines, and is there anything Microsoft 365 customers can do about it?
What can we do about Microsoft sending IPs with no PTR record?
Answers
Open a Microsoft support ticket with the affected sending IPs, full message headers, UTC timestamps and the results of reverse DNS lookups against the authoritative servers. Microsoft controls the PTR records for its outbound IPs, so customers can't add them themselves.
Recheck the addresses before submitting the ticket. One address in the reported sample gained a PTR between checks, so the DNS state may be changing.
Reply to this answer
I'd separate the DNS finding from the policy outcome. A missing PTR is a concrete configuration issue, but check the exact Spamhaus guideline and enforcement wording before assuming every affected IP will automatically be listed.
Also, a DMARC pass doesn't tell you whether reverse DNS is present or whether the SMTP greeting meets a sender guideline. Those need separate checks.
Reply to this answer
Make sure you're checking the right problem. An IP with no PTR at all isn't the same thing as an IP whose PTR hostname differs from its SMTP greeting. A reverse lookup can distinguish those cases, and a forward lookup of the PTR hostname can check whether it resolves back to the sending IP.
Reply to this answer
The reported sample was small relative to the total Microsoft mail volume examined, but that doesn't mean an affected message can't run into trouble. Keep an eye on delivery failures and include the sending IP and recipient response in any support report rather than assuming every failure has the same cause.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions