spamhaus check not working

John R. Levine
Sat Jul 1 21:37:58 UTC 2017

> Just to follow up on this.  I finally realized the problem was that the machine in question was set up to use as its local DNS resolver and not, i.e. recurse all the way to Spamhaus via its own bind/named instance.  This was causing false negatives, i.e. would not resolve to 127.0.0.x for some reason.  I guess this isn't supported for whatever reason?

Spamhaus rate limits free users, so public resolvers like are 
always over their rate limits.


More information about the DCC mailing list

Contact by mail or use the form.