False alarms about incorrect reverse DNS

Every couple of days, my box alternates between:
:heavy_multiplication_x: Your box’s reverse DNS is currently [Not Set], but it should be mail.acedb.co. Your ISP or cloud provider will have instructions on setting up reverse DNS for your box.
and:
✓ Reverse DNS is set correctly at ISP. [146.229.97.10 ↦ mail.acedb.co]

Every time I check it, the reverse DNS is working fine. The owner of my IPs is not making any changes. Any ideas what could be causing this? I have NOT altered the address or host name in case anyone would like to look at how my DNS is set up.

Might find some help from one of these previous reports:

Seems to be a common occurence for Digital Ocean installs.

I have run several different installs of MiaB … and have gotten the same warnings.

Over time, I just simply learned to ignore them.

1 Like

I ran into the system check warning about my reverse dns on VULTR hosting being wrong about a week after everything was perfect on initial setup. I added the instance IP on the rDNS field x.x.x.x.box.domain.com and then saw my mail deliverability score drop due to IP mismatch to PTR with the IP. VULTR saw no issue in a ticket I sent them so I put the VULTR rDNS field back to box.domain.com (domain=my actual domain) and tested again using mail-tester.com and got back up to 10/10 good deliverability.

The rDNS requirement is just to have one. I have webserver that sends transactional email for ~12 domains. Never have anything declared as spam from that server despite the fact that the rDNS doesn’t doesn’t match.

That said, not having the record is almost guaranteed to result in spam.

I saw this issue corrected later today and advised VULTR in case they knew of something that had changed. While testing earlier with them their test of

dig -x x.x.x.x @1.1.1.1 (x.x.x.x = my instance IP) resulted in a Answer record for PTR while mine didn’t.

They reply to my update saying they had been made aware of an issue with their DNS earlier today (I assume me) and corrected it. So I guess it’s worth contacting the host (as the MaiB message advises) just in case there’s something a miss on their end. Just wanted to update this topic for other to see this outcome.

I have the same issue with Strato.
Now and then I get that message. Most of the time for IPv6.

Not really a problem so far. Maybe the check mechanism should do a retry once or twice?

@JoshData