On 2/8/2006 11:56 PM +0100, Todd Lyons wrote:
Let's not rule out the possibility of dns cache poisoning. If you're
not running a recent version of whatever dns server you are using, it
could be susceptible to this, and it could be someone experimenting with
attempting to fool your freshclam process into thinking that it's
current (by feeding bogus information to your nameservers). I know of
nobody claiming to have seen such a thing, but it is _possible_ and so
therefore it should at least be looked at.
dig +short @ns1.clamav.net txt current.cvd.clamav.net
"0.88:35:1278:1139243341:1"
dig +short @ns2.clamav.net txt current.cvd.clamav.net
"0.88:35:1281:1139437741:1"
ns3 till ns7 show what ns2 shows.
So there's definitely something wrong with ns1.
Regards,
Niek Baakman
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
