Re: [clamav-users] A workaround for the major ClamAV DB update delays we have been experiencing

2018-12-08 Thread Joel Esler (jesler)
Not sure what you’re saying here. Are you saying that the daily on the cache is out of date? Sent from my  iPhone > On Dec 8, 2018, at 20:30, Eric Tykwinski wrote: > > J.R. > > You are falling into the same trap I followed. The txt record is: > current.cvd.clamav.net.1749INTXT

Re: [clamav-users] A workaround for the major ClamAV DB update delays we have been experiencing

2018-12-08 Thread Eric Tykwinski
J.R. You are falling into the same trap I followed. The txt record is: current.cvd.clamav.net.1749IN 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 Trying 104.16.185.138... Connected to

Re: [clamav-users] A workaround for the major ClamAV DB update delays we have been experiencing

2018-12-08 Thread J.R.
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

Re: [clamav-users] A workaround for the major ClamAV DB update delays we have been experiencing

2018-12-08 Thread Eric Tykwinski
Paul, Sorry I got it backwards, I thought you were saying the TXT record was different which would be effected by DNS caching. The CloudFlare cache would definitely effect daily.cvd, but updates are new. Only way I could see you get around it yourself is to create your own cdiff program from

Re: [clamav-users] A workaround for the major ClamAV DB update delays we have been experiencing

2018-12-08 Thread Paul Kosinski
Not sure what DNS caching would have to do with this. As I understand "anycast", it happens at the IP address level. An anycast IP address gets routed differently depending are where you are -- different (regional) routers have different "next hops" for the IP address, and it eventually ends up at

Re: [clamav-users] Can't detect deceptive URL's as infected !!

2018-12-08 Thread Micah Snyder (micasnyd)
Our replies may be getting filtered by your email provider because you included a malicious link in the email chain. :D I removed the link from this reply. Micah Snyder ClamAV Development Talos Cisco Systems, Inc. On Dec 8, 2018, at 9:17 AM, Sunny Marwah mailto:sunnymar...@trepup.com>>

Re: [clamav-users] Can't detect deceptive URL's as infected !!

2018-12-08 Thread Sunny Marwah
Still no reply on this matter. On Fri, Dec 7, 2018 at 6:17 PM Sunny Marwah wrote: > Hi Al Varnell, > > Below is the URL which was mentioned in HTML template : > > https://gokdenizhealthtourism.com/js/logo2.gif > > Chrome don't open it due to labeling it dangerous in as per > "Safebrowsing".