On 17/05/17 16:53, David Mehler wrote:
Hi,
I don't see your SA issue here, but since your running 3.41 can I get
a look at your SA configuration to compare against mine?
Thanks.
Dave.
Yes - you are correct. As I pointed out in my last email, it looks like
there might be an issue with the package supplied by Slackware at
slackbuilds.org - and I am chasing it up with them there. But thanks to
the advice on this list, I've managed to narrow things down - so I am
grateful for the hints.
On 5/17/17, Sebastian Arcus <s.ar...@open-t.co.uk> wrote:
On 17/05/17 14:54, Sebastian Arcus wrote:
On 17/05/17 14:21, Kevin A. McGrail wrote:
On 5/17/2017 8:22 AM, Sebastian Arcus wrote:
I have 2 servers with SA 3.4.1 running on Slackware, with Bind in
caching/recursive mode. For months one of them has been unable to
correctly do dns blocklists (but the queries are not blocked). I have
pored over the logs, and the main difference is that, although both
of them pick up on the bad urls in the body of the message, the bad
server is unable to resolve the url to an IP address for some reason
(but dig works fine on the command line on both servers):
What version of Net::DNS on the two boxes? Does the 3.4 branch from
SVN work?
There have been changes to Net::DNS that are my likely first guess.
Thank you for the suggestion. I have Net::DNS 1.10. I have just
recompiled SA from SVN and it is using dnsrbl's correctly. Have there
been some changes in the way SA works recently?
A small update to this - I recompiled 3.4.1 by hand - and this is
working fine as well. This would suggest that the Slackware package is
somehow the problem - unless it is all coincidental and I am somehow
chasing my own tail. I will update here if I find out more. Thank you
again for the suggestion.
