[clamav-users] A workaround for the major ClamAV DB update delays we have been experiencing
eric-list at truenet.com
Sat Dec 8 20:24:26 EST 2018
You are falling into the same trap I followed. The txt record is:
current.cvd.clamav.net. 1749 IN TXT "0.101.0:58:25189:1544315340:1:63:48210:327"
But host headers is what he’s looking at:
telnet database.clamav.net 80
Connected to database.clamav.net.cdn.cloudflare.net.
Escape character is '^]'.
GET /daily.cvd HTTP/1.1
HTTP/1.1 200 OK
Date: Sun, 09 Dec 2018 01:18:51 GMT
Set-Cookie: __cfduid=ddc4d2ab2a13638c99a90bb14c12128971544318331; expires=Mon, 09-Dec-19 01:18:51 GMT; path=/; domain=.clamav.net; HttpOnly
Last-Modified: Sat, 08 Dec 2018 18:18:00 GMT
Expires: Sun, 09 Dec 2018 05:05:51 GMT
Cache-Control: public, max-age=13620
ClamAV-VDB:08 Dec 2018 13-18 -0500:25189:2177974:63:2e2e28a4556e83e2df68c40fa61566d4:nWqDCF65xA9fMhiKYOtZhH8Up6lAHLrl6VyCrXRAXCB7aMf7WqSPrwMz/YHhdgKSNjxGiL8Z2ORQ2aPm23KwqwyJUpOZv94+soWx+NibPlKBPJ6/ZAt9Z5UrhgDbgz0IVQsHX998ZjBE6NY6xtqfzboOPNKyeFINLeAUL5hSpzj:neo:1544293134
So daily.cvd is being cached on cloudflare for the first update and you might need to be running a freshclam right after a new install since it’s out of date due to caching on cloudflare’s server.
> On Dec 8, 2018, at 7:30 PM, J.R. <themadbeaker at gmail.com> wrote:
> I've kind of been reading this thread about the delay at one location
> vs the other.
> Maybe I missed it, but I don't seem to recall which DNS servers you
> were querying. I remember you saying the one location you were having
> the issues was Comcast as the ISP, but were you always using the
> Comcast DNS or did you try others like 188.8.131.52 or 184.108.40.206 ?
> Or was the DNS saying there was a newer version but when you queried
> cloudflare it was reporting differently?
> clamav-users mailing list
> clamav-users at lists.clamav.net
> Help us build a comprehensive ClamAV guide:
More information about the clamav-users