My mail server uses a public DNS resolver for blacklist checks. Can that make Spamhaus lookups fail silently, and what's a quick way to check?
Can public DNS make Spamhaus checks look clean when they aren't?
Answers
Yes. Spamhaus can restrict queries coming through shared public resolvers, including Google and Cloudflare. Depending on the response and how your checker handles it, a failed lookup might be treated as a clean result instead of an error.
Run dig +short 2.0.0.127.zen.spamhaus.org on the mail server using the same resolver as your mail software. It's a test entry and should include 127.0.0.2. You may see other listed response codes too. An empty result or a 127.255.255.x response needs investigation, not a clean verdict.
Reply to this answer
Run your own recursive resolver and point the mail server at it. Unbound is one option. That avoids sending the checks through a large shared public resolver, though you should still test the lookup and make sure your query volume meets Spamhaus's access rules.
q.638~buttonwhisk:
Spamhaus DQS is another route. Check its eligibility and usage terms before choosing a key.
Reply to this answer
For a blacklist checker, the bigger design issue is treating every missing answer as not listed. Test each list against its documented test entry and show a lookup failure separately from a clean result. Otherwise a broken resolver path can make the whole dashboard look reassuring.
Reply to this answer
I wouldn't assume the public resolver is deliberately altering the answer. Spamhaus may be restricting queries from a shared resolver or applying query limits. The practical issue is that many users' lookups can appear to come from the same resolver.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_c52+plumvisor.7:
Check the actual resolver path too. A test from another machine or through a different resolver won't necessarily tell you what the mail server sees.