All this is true.
As you already pointed out in a previous post, resolving is quite slow
on that host. I have no influence on the networking arround that box. So
I did not want other things starting to go slow by this.
But you convinced me - I now also thing that the other way bears too
much stumbling blocks.
Marc
Am 16.09.2015 um 13:43 schrieb Reindl Harald:
Am 16.09.2015 um 13:38 schrieb Marc Richter:
Am 16.09.2015 um 11:41 schrieb Axb:
Although, the intended setup with exemptions by defining empty
forwarders for DNSBL zones was not my idea - this scenario is described
on the SA wiki as a working solution:
http://wiki.apache.org/spamassassin/CachingNameserver#Non-forwarding
This seems to not be working, so I'm heading for this ML to find out
why.
are you doing this:
zone "multi.uribl.com" { type forward; forward first; forwarders {}; };
if yes try adding:
zone "uribl.com" { type forward; forward first; forwarders {}; };
looks like this is it! I changed this as suggested and send myself some
spams. The DNSBL Checks are working now, Thank you :)
you need to maintain this everytime domains / subdomains are changing
and probably new lists are added - you need to take care about all of
this when rule-updates arrive
* what about barracuda RBL
* what about mailspike
both used in SA and not mentioned there
a local unbound cache with 64-128 MB RAM and a minimal TTL of 10 minutes
would save you a lot of headache and result in even better caching
