I’m a +1 here. Since setting up MIAB v0.12c in August, also on DigitalOcean, I’ve been receiving this alert regularly. I asked DigitalOcean to confirm on their end that the PTR was correct and they affirmed. I also see it set correctly when testing from my own network. Edit: This persists through to the latest version of MIAB.
I have noted that as of August DigitalOcean’s DNS panel refuses to create zones when a droplet’s FQDN is a second level domain (e.g. example.tld) and I wonder if there is some related bug in their PTR maintenance code…? This was of interest to me because I bought and am using a .com for the server itself. Is this the same for everyone else, or are you using subdomains?
All the reports here so far are also from DigitalOcean customers. @JoshData are you tracking this from users of any other provider?