Thank you -- did not realise the /etc/default/unbound file existed. It was
set to forward. Will remind me how I prefer instllatins from source for
critical programs.
Unbound installed from Debian Whezzy
On Sat, 4 Jun 2016, Tom Hendrikx wrote:
On 03-06-16 18:19, jpff wrote:
X-Originating-<%= hostname %>-IP: [217.155.197.248]
OK I expect to get flamed but anyway....
I run a couple of mailers, one of which is small with ~5 users. For
years I ran dnsmasq which was easy to set up and only gave occasional
troubles with the RBL lookups being rejected from my ISP (hi Zen!). I
knew why but it did not seem to cause much problem in stopping spam.
But with the latest outbreak of discussion and some spare time I
changed to use unbound which was suggested by someone. Apart from one
semi-error in the instructions it was easy to deploy
BUT....
I as still seeing the occasional URIBL_BLOCKED
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was
blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: zakofr.top]
I thought the recursive caching dns system was supposed to remove
this. Just seeking enlightenment.
==John ffitch
Which OS is this? The default setting on ubuntu 14.04 for unbound was
unfortunately that the init script automatically added upstream dns
servers as forwarders, which effectively mimics the dnsmasq behaviour
that gives troubles for spamassassin.
To fix that behaviour, set RESOLVCONF_FORWARDERS=false in
/etc/default/unbound, and restart unbound.
Regards,
Tom
