Hi,

For the past few weeks I've been having problems with queries to many
of the common RBLs, including barracuda, mailspike and unsubscore. My
logs are filled with "Name service error", SERVFAIL and lame-server
messages for RBLs I know to be valid.

14-Sep-2018 12:21:10.928 query-errors: info: client @0x7f105735f3b0
127.0.0.1#44791 (139.33.47.104.bl.mailspike.net): query failed
(SERVFAIL) for 139.33.47.104.bl.mailspike.net/IN/A at
../../../bin/named/query.c:8580
14-Sep-2018 12:21:10.928 query-errors: info: client @0x7f10342d4650
127.0.0.1#44791 (139.33.47.104.db.wpbl.info): query failed (SERVFAIL)
for 139.33.47.104.db.wpbl.info/IN/A at ../../../bin/named/query.c:8580
14-Sep-2018 12:21:10.928 query-errors: debug 2: fetch completed at
../../../lib/dns/resolver.c:3927 for 139.33.47.104.bl.mailspike.net/A
in 30.000146: timed out/success
[domain:bl.mailspike.net,referral:0,restart:5,qrysent:14,timeout:13,lame:0,quota:0,neterr:0,badresp:0,adberr:0,findfail:0,valfail:0]

This shows a failure while other times these same queries succeed.

This is using bind set up as a standard recursive name server on
fedora28. These are bind logs, but does anyone know why spamassassin
queries to these RBLs would timeout? There's no firewall involved. It
appears to happen at all times during the day.

I really have no other ideas after staring at the logs for weeks,
seeing it happen on all my systems, and asking on numerous other lists
(including postfix and bind-users).

Reply via email to