if your blacklist checker uses Google or Cloudflare DNS, Spamhaus results are probably wrong
retained text
Ran into this while chasing a bug report and it surprised me, so sharing. Spamhaus doesn't answer queries that come through big public resolvers. Google returns an empty answer, which your software reads as "not listed". So a Postfix reject\_rbl\_client zen.spamhaus.org on a box that resolves through 8.8.8.8 lets everything through, and nothing ever logs an error. 10-second test, run on your mail server: dig +short [2.0.0.127.zen.spamhaus.org](http://2.0.0.127.zen.spamhaus.org) That's Spamhaus's permanent test entry; it should always return 127.0.0.2. Empty or 127.255.255.x means your lookups aren't working. Fix: run a local recursive resolver (Unbound takes five minutes) and point the mail server at it. If you're non-commercial, a free Spamhaus DQS key also works. How I found it: I maintain a small self-hosted blacklist monitor, and a user reported an IP that was on Spamhaus but showed clean. Same cause. It now tests every list against its test address first and shows "no answer" instead of a fake "clean". Curious how common this is: what does the dig return for you?
document fetched 2026-10-27 00:38 · canonical https://reddit.com/r/sysadmin/comments/1xfnayk/if_your_blacklist_checker_uses_google_or