Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-13 Thread Joel Esler (jesler) 
Bill,

We have taken some recent steps to resolve these issues.  Please let us know if 
they persist.

Sent from my iPhone

On Nov 13, 2017, at 5:37 PM, Bill Maidment 
<b...@maidment.me<mailto:b...@maidment.me>> wrote:

I'm still getting a mixed bag of results on db.AU
Sometimes it works and other times I get the following:

Mon Nov 13 18:21:35 2017 -> ClamAV update process started at Mon Nov 13 
18:21:35 2017
Mon Nov 13 18:21:35 2017 -> main.cld is up to date (version: 58, sigs: 4566249, 
f-level: 60, builder: sigmgr)
Mon Nov 13 18:22:12 2017 -> nonblock_recv: recv timing out (30 secs)
Mon Nov 13 18:22:12 2017 -> WARNING: getfile: Error while reading database from 
db.AU.clamav.net<http://db.AU.clamav.net> (IP: 128.199.133.36): Operation now 
in progress
Mon Nov 13 18:22:12 2017 -> WARNING: getpatch: Can't download daily-24039.cdiff 
from db.AU.clamav.net<http://db.AU.clamav.net>
Mon Nov 13 18:22:13 2017 -> WARNING: getfile: daily-24039.cdiff not found on 
db.AU.clamav.net<http://db.AU.clamav.net> (IP: 72.21.91.8)
Mon Nov 13 18:22:13 2017 -> WARNING: getpatch: Can't download daily-24039.cdiff 
from db.AU.clamav.net<http://db.AU.clamav.net>
Mon Nov 13 18:22:14 2017 -> Downloading daily-24039.cdiff [100%]
Mon Nov 13 18:22:16 2017 -> daily.cld updated (version: 24039, sigs: 1778849, 
f-level: 63, builder: neo)
Mon Nov 13 18:22:16 2017 -> bytecode.cld is up to date (version: 318, sigs: 75, 
f-level: 63, builder: raynman)
Mon Nov 13 18:22:22 2017 -> Database updated (6345173 signatures) from 
db.AU.clamav.net<http://db.AU.clamav.net> (IP: 198.148.78.4)
Mon Nov 13 21:21:34 2017 -> --
Mon Nov 13 21:21:34 2017 -> ClamAV update process started at Mon Nov 13 
21:21:34 2017
Mon Nov 13 21:21:34 2017 -> WARNING: DNS record is older than 3 hours.
Mon Nov 13 21:21:34 2017 -> WARNING: Invalid DNS reply. Falling back to HTTP 
mode.
Mon Nov 13 21:21:34 2017 -> Reading CVD header (main.cvd): Mon Nov 13 21:21:35 
2017 -> OK (IMS)
Mon Nov 13 21:21:35 2017 -> main.cld is up to date (version: 58, sigs: 4566249, 
f-level: 60, builder: sigmgr)
Mon Nov 13 21:21:35 2017 -> Reading CVD header (daily.cvd): Mon Nov 13 21:21:35 
2017 -> OK
Mon Nov 13 21:21:35 2017 -> daily.cld is up to date (version: 24039, sigs: 
1778849, f-level: 63, builder: neo)
Mon Nov 13 21:21:35 2017 -> Reading CVD header (bytecode.cvd): Mon Nov 13 
21:21:36 2017 -> OK
Mon Nov 13 21:21:36 2017 -> bytecode.cld is up to date (version: 318, sigs: 75, 
f-level: 63, builder: raynman)



-Original message-
From:Groach 
<groachmail-stopspammin...@yahoo.com<mailto:groachmail-stopspammin...@yahoo.com>>
Sent: Tuesday 14th November 2017 6:56
To: clamav-users@lists.clamav.net<mailto:clamav-users@lists.clamav.net>
Subject: Re: [clamav-users] FreshClam - DNS issues since October 31st

On 08/11/2017 21:18, Jeff wrote:
The last three updates did not have the error. Below is the last error I got:

--
ClamAV update process started at Wed Nov 08 13:13:12 2017

Its ok for me too (not returning DNS errors).  (But it says something
about 'cdiff not foundcant download from remote server' from one
server. But thats another thing).

ClamAV update process started at Tue Nov 07 21:58:00 2017
main.cld is up to date (version: 58, sigs: 4566249, f-level: 60,
builder: sigmgr)
WARNING: getfile: daily-24020.cdiff not found on remote server (IP:
193.1.193.64)
WARNING: getpatch: Can't download daily-24020.cdiff from 
database.clamav.net<http://database.clamav.net>
Trying host database.clamav.net<http://database.clamav.net> (129.67.1.218)...
Downloading daily-24020.cdiff [100%]
Downloading daily-24021.cdiff [100%]
Downloading daily-24022.cdiff [100%]
Downloading daily-24023.cdiff [100%]
daily.cld updated (version: 24023, sigs: 1774015, f-level: 63, builder: neo)
Downloading bytecode-317.cdiff [100%]
Downloading bytecode-318.cdiff [100%]
bytecode.cld updated (version: 318, sigs: 75, f-level: 63, builder: raynman)
Database updated (6340339 signatures) from 
database.clamav.net<http://database.clamav.net> (IP:
129.67.1.218)

___
clamav-users mailing list
clamav-users@lists.clamav.net<mailto:clamav-users@lists.clamav.net>
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users

Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml


___
clamav-users mailing list
clamav-users@lists.clamav.net<mailto:clamav-users@lists.clamav.net>
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
___
clamav-users mailing list
clamav-users@l

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-13 Thread Bill Maidment 
I'm still getting a mixed bag of results on db.AU
Sometimes it works and other times I get the following:

Mon Nov 13 18:21:35 2017 -> ClamAV update process started at Mon Nov 13 
18:21:35 2017
Mon Nov 13 18:21:35 2017 -> main.cld is up to date (version: 58, sigs: 4566249, 
f-level: 60, builder: sigmgr)
Mon Nov 13 18:22:12 2017 -> nonblock_recv: recv timing out (30 secs)
Mon Nov 13 18:22:12 2017 -> WARNING: getfile: Error while reading database from 
db.AU.clamav.net (IP: 128.199.133.36): Operation now in progress
Mon Nov 13 18:22:12 2017 -> WARNING: getpatch: Can't download daily-24039.cdiff 
from db.AU.clamav.net
Mon Nov 13 18:22:13 2017 -> WARNING: getfile: daily-24039.cdiff not found on 
db.AU.clamav.net (IP: 72.21.91.8)
Mon Nov 13 18:22:13 2017 -> WARNING: getpatch: Can't download daily-24039.cdiff 
from db.AU.clamav.net
Mon Nov 13 18:22:14 2017 -> Downloading daily-24039.cdiff [100%]
Mon Nov 13 18:22:16 2017 -> daily.cld updated (version: 24039, sigs: 1778849, 
f-level: 63, builder: neo)
Mon Nov 13 18:22:16 2017 -> bytecode.cld is up to date (version: 318, sigs: 75, 
f-level: 63, builder: raynman)
Mon Nov 13 18:22:22 2017 -> Database updated (6345173 signatures) from 
db.AU.clamav.net (IP: 198.148.78.4)
Mon Nov 13 21:21:34 2017 -> --
Mon Nov 13 21:21:34 2017 -> ClamAV update process started at Mon Nov 13 
21:21:34 2017
Mon Nov 13 21:21:34 2017 -> WARNING: DNS record is older than 3 hours.
Mon Nov 13 21:21:34 2017 -> WARNING: Invalid DNS reply. Falling back to HTTP 
mode.
Mon Nov 13 21:21:34 2017 -> Reading CVD header (main.cvd): Mon Nov 13 21:21:35 
2017 -> OK (IMS)
Mon Nov 13 21:21:35 2017 -> main.cld is up to date (version: 58, sigs: 4566249, 
f-level: 60, builder: sigmgr)
Mon Nov 13 21:21:35 2017 -> Reading CVD header (daily.cvd): Mon Nov 13 21:21:35 
2017 -> OK
Mon Nov 13 21:21:35 2017 -> daily.cld is up to date (version: 24039, sigs: 
1778849, f-level: 63, builder: neo)
Mon Nov 13 21:21:35 2017 -> Reading CVD header (bytecode.cvd): Mon Nov 13 
21:21:36 2017 -> OK
Mon Nov 13 21:21:36 2017 -> bytecode.cld is up to date (version: 318, sigs: 75, 
f-level: 63, builder: raynman)

 
 
-Original message-
> From:Groach <groachmail-stopspammin...@yahoo.com>
> Sent: Tuesday 14th November 2017 6:56
> To: clamav-users@lists.clamav.net
> Subject: Re: [clamav-users] FreshClam - DNS issues since October 31st
> 
> On 08/11/2017 21:18, Jeff wrote:
> > The last three updates did not have the error. Below is the last error I 
> > got:
> >
> > --
> > ClamAV update process started at Wed Nov 08 13:13:12 2017
> 
> Its ok for me too (not returning DNS errors).  (But it says something 
> about 'cdiff not foundcant download from remote server' from one 
> server. But thats another thing).
> 
> ClamAV update process started at Tue Nov 07 21:58:00 2017
> main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, 
> builder: sigmgr)
> WARNING: getfile: daily-24020.cdiff not found on remote server (IP: 
> 193.1.193.64)
> WARNING: getpatch: Can't download daily-24020.cdiff from database.clamav.net
> Trying host database.clamav.net (129.67.1.218)...
> Downloading daily-24020.cdiff [100%]
> Downloading daily-24021.cdiff [100%]
> Downloading daily-24022.cdiff [100%]
> Downloading daily-24023.cdiff [100%]
> daily.cld updated (version: 24023, sigs: 1774015, f-level: 63, builder: neo)
> Downloading bytecode-317.cdiff [100%]
> Downloading bytecode-318.cdiff [100%]
> bytecode.cld updated (version: 318, sigs: 75, f-level: 63, builder: raynman)
> Database updated (6340339 signatures) from database.clamav.net (IP: 
> 129.67.1.218)
> 
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml
> 
> 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-13 Thread Groach 



On 08/11/2017 21:18, Jeff wrote:

The last three updates did not have the error. Below is the last error I got:

--
ClamAV update process started at Wed Nov 08 13:13:12 2017


Its ok for me too (not returning DNS errors).  (But it says something 
about 'cdiff not foundcant download from remote server' from one 
server. But thats another thing).



ClamAV update process started at Tue Nov 07 21:58:00 2017
main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, 
builder: sigmgr)
WARNING: getfile: daily-24020.cdiff not found on remote server (IP: 
193.1.193.64)

WARNING: getpatch: Can't download daily-24020.cdiff from database.clamav.net
Trying host database.clamav.net (129.67.1.218)...
Downloading daily-24020.cdiff [100%]
Downloading daily-24021.cdiff [100%]
Downloading daily-24022.cdiff [100%]
Downloading daily-24023.cdiff [100%]
daily.cld updated (version: 24023, sigs: 1774015, f-level: 63, builder: neo)
Downloading bytecode-317.cdiff [100%]
Downloading bytecode-318.cdiff [100%]
bytecode.cld updated (version: 318, sigs: 75, f-level: 63, builder: raynman)
Database updated (6340339 signatures) from database.clamav.net (IP: 
129.67.1.218)


___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-10 Thread Dennis Peterson 

I've never had a successful download from that ip.

dp

On 11/9/17 11:36 PM, Al Varnell wrote:

As you probably already know, in past discussions of the US round robin it was 
revealed that there weren't enough US mirrors to support the demand and that 
was the primary reason for including low demand off-shore servers as 
supplements to handle the over-flow. I don't know whether that situation still 
exists now that Cisco has assumed responsibility for the network.

Certainly true that Singapore is a long way from Kansas and a quick traceroute 
revealed a lot of bouncing around ending in considerable latency:




___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-09 Thread Al Varnell 
As you probably already know, in past discussions of the US round robin it was 
revealed that there weren't enough US mirrors to support the demand and that 
was the primary reason for including low demand off-shore servers as 
supplements to handle the over-flow. I don't know whether that situation still 
exists now that Cisco has assumed responsibility for the network.

Certainly true that Singapore is a long way from Kansas and a quick traceroute 
revealed a lot of bouncing around ending in considerable latency:

> Trace route (tcp) Payload: 64 Interface: en1 10.0.1.127
> to: 128.199.133.36:80 (128.199.133.36)
> 
>  1 10.0.1.1   3.004 ms0.879 ms
> 0.820 ms
>  2 96.120.89.145 [AS7922] (US)9.855 ms   10.293 ms   
> 12.919 ms
>  3 be-20003-sur04.santaclara.ca.sfba.comcast.net (68.86.249.249) [AS7922] (US)
>   9.854 ms   15.705 ms
> 9.789 ms
>  4 be-332-ar01.hayward.ca.sfba.comcast.net (162.151.79.157) [AS7922] (US)
>  12.421 ms   11.589 ms   
> 13.443 ms
>  5 be-3651-cr01.9greatoaks.ca.ibone.comcast.net (68.86.91.65) [AS7922] (US)
>  15.202 ms   16.020 ms   
> 15.877 ms
>  6 hu-0-10-0-1-pe03.11greatoaks.ca.ibone.comcast.net (68.86.85.234) [AS7922] 
> (US)
>  14.962 ms   13.651 ms   
> 12.965 ms
>  7 ae-13.a02.snjsca04.us.bb.gin.ntt.net (129.250.66.33) [AS2914] (US)
>  14.192 ms   16.465 ms   
> 14.268 ms
>  8 ae-4.r02.snjsca04.us.bb.gin.ntt.net (129.250.3.102) [AS2914] (US)
>  13.502 ms
>  8 ae-9.r01.snjsca04.us.bb.gin.ntt.net (129.250.2.2) [AS2914] (US)
>  21.212 ms   12.815 ms
>  9 ae-1.r22.snjsca04.us.bb.gin.ntt.net (129.250.3.26) [AS2914] (US)
>  12.953 ms   14.005 ms
> 10 ae-2.r20.sngpsi05.sg.bb.gin.ntt.net (129.250.3.49) [AS2914] (US)
> 209.130 ms  201.054 ms  
> 210.069 ms
> 11 ae-1.r00.sngpsi05.sg.bb.gin.ntt.net (129.250.7.19) [AS2914] (US)
> 187.140 ms  178.793 ms  
> 182.803 ms
> 12 ae-0.a00.sngpsi05.sg.bb.gin.ntt.net (129.250.7.9) [AS2914] (US)
> 183.783 ms  190.572 ms  
> 179.938 ms
> 13 ae-6.r01.sngpsi07.sg.bb.gin.ntt.net (129.250.7.26) [AS2914] (US)
> 189.889 ms  199.520 ms  
> 201.603 ms
> 14 ae-1.a00.sngpsi07.sg.bb.gin.ntt.net (129.250.2.92) [AS2914] (US)
> 177.902 ms  192.850 ms
> 14 unknown.a01.sngpsi07.sg.bb.gin.ntt.net (129.250.2.240) [AS2914] (US)
> 183.668 ms
> 15 116.51.17.194 [AS2914] (SG)  191.202 ms
> 15 ae-0.digital-ocean.sngpsi07.sg.bb.gin.ntt.net (116.51.17.166) [AS2914] (SG)
> 188.870 ms
> 15 116.51.17.194 [AS2914] (SG)  180.435 ms
> 16   *   *
>*
> 17   *   *
>*
> 18   *   *
>*
> 19 128.199.133.36 [open] [AS14061] (SG) 197.110 ms  187.651 ms  
> 195.759 ms
> 
> Reached target: 128.199.133.36
> Elapsed (sec): 17.444

Since I rarely use the ClamAV network for updates these days, I don't have a 
valid mirrors.dat that shows statistics on 128.199.133.36. Is a high failure 
rate the basis of your request?

-Al-

On Thu, Nov 09, 2017 at 09:06 PM, Dennis Peterson wrote:
> Any chance you can remove 128.199.133.36  from the US round robin? It's a 
> long way from Kansas.
> 
> dp
> 
> 
> On 11/8/17 7:50 AM, Joel Esler (jesler) wrote:
>> The team working on these issues is seeing these emails, so it’s good that 
>> you are writing in, if you are still experiencing issues.


smime.p7s
Description: S/MIME cryptographic signature
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-09 Thread Dennis Peterson 
Any chance you can remove 128.199.133.36  from the US round robin? It's a long 
way from Kansas.


dp


On 11/8/17 7:50 AM, Joel Esler (jesler) wrote:

The team working on these issues is seeing these emails, so it’s good that you 
are writing in, if you are still experiencing issues.



___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-09 Thread Noel Jones 
Getting errors off-and-on since about 3am CDT today.

But working right now.

Obviously something still not right.



  -- Noel Jones



On 11/8/2017 2:51 PM, Noel Jones wrote:
> It's working now.  The last error in the log was about 30 minutes
> after the report below.
> 
> Thanks.
> 
> Location is US central time zone with local DNS resolver FWIW.
> 
> 
>   -- Noel Jones
> 
> 
> 
> On 11/8/2017 1:47 PM, David Raynor wrote:
>> The DNS records are being updated at the source properly now. If you are
>> still seeing an error, then the proper record is not reaching the server
>> you are contacting for DNS or not propagating correctly to your area or
>> something like that.
>>
>> If you are still seeing those errors, let us know what the value of the DNS
>> TXT record you are seeing for current.cvd.clamav.net. You can use "host" or
>> "dig" or another command to check it.
>>
>> Example (with current value):
>>
>> $ host -t txt current.cvd.clamav.net
>> current.cvd.clamav.net descriptive text
>> "0.99.2:58:24025:1510165084:1:63:46630:318"
>>
>> Dave R.
>>
>> On Wed, Nov 8, 2017 at 11:34 AM, Noel Jones  wrote:
>>
>>> I'm still getting these errors too.   :\
>>>
>>>
>>>
>>>
>>>   -- Noel Jones
>>>
>>>
>>> On 11/8/2017 9:50 AM, Joel Esler (jesler) wrote:
 The team working on these issues is seeing these emails, so it’s good
>>> that you are writing in, if you are still experiencing issues.

>>> ___
>>> clamav-users mailing list
>>> clamav-users@lists.clamav.net
>>> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>>>
>>>
>>> Help us build a comprehensive ClamAV guide:
>>> https://github.com/vrtadmin/clamav-faq
>>>
>>> http://www.clamav.net/contact.html#ml
>>>
>>
>>
>>
> 
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml
> 

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-09 Thread Simon Mousey Smith 
Hi,

We started seeing the same problem here

It was fine during the night but then this morning started again with the 
WARNING messages?

[root@mailgw ~]# host -t txt current.cvd.clamav.net
current.cvd.clamav.net descriptive text 
"0.99.2:58:24027:1510207861:1:63:46632:318"
[root@mailgw ~]# date
Thu Nov  9 10:27:43 GMT 2017
[root@mailgw ~]# 

Regards

Simon

> On 9 Nov 2017, at 10:05, Adolf Belka  wrote:
> 
> I am still seeing the message. Periodically it stops and when I check that is 
> when the time from the DNS record has become closer to my computers time but 
> then the delta progressively increases and exceeds the 3 hours and the 
> message starts again. Today it started again at 10:12 (Netherlands time 
> zone). At 9:56 it was fine.
> 
> Here is the DNS TXT value I get:-
> 
> current.cvd.clamav.net descriptive text 
> "0.99.2:58:24027:1510207861:1:63:46632:318"
> 
> My current computer time was 1510221600.
> 
> The following came from the dig command:-
> 
> ; <<>> DiG 9.9.5-3ubuntu0.16-Ubuntu <<>> current.cvd.clamav.net
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20331
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4096
> ;; QUESTION SECTION:
> ;current.cvd.clamav.net.INA
> 
> ;; AUTHORITY SECTION:
> cvd.clamav.net.3600INSOAns3.clamav.net. 
> hostmaster.oltrelinux.com. 2006375260 1800 900 604800 7200
> 
> ;; Query time: 281 msec
> ;; SERVER: 192.168.26.254#53(192.168.26.254)
> ;; WHEN: Thu Nov 09 11:03:50 CET 2017
> ;; MSG SIZE  rcvd: 116
> 
> Regards,
> 
> Adolf Belka
> 
> Sent from my Desktop Computer
> 
> On 08/11/17 20:47, David Raynor wrote:
>> The DNS records are being updated at the source properly now. If you are
>> still seeing an error, then the proper record is not reaching the server
>> you are contacting for DNS or not propagating correctly to your area or
>> something like that.
>> 
>> If you are still seeing those errors, let us know what the value of the DNS
>> TXT record you are seeing for current.cvd.clamav.net. You can use "host" or
>> "dig" or another command to check it.
>> 
>> Example (with current value):
>> 
>> $ host -t txt current.cvd.clamav.net
>> current.cvd.clamav.net descriptive text
>> "0.99.2:58:24025:1510165084:1:63:46630:318"
>> 
>> Dave R.
>> 
>> On Wed, Nov 8, 2017 at 11:34 AM, Noel Jones  wrote:
>> 
>>> I'm still getting these errors too.   :\
>>> 
>>> 
>>> 
>>> 
>>>   -- Noel Jones
>>> 
>>> 
>>> On 11/8/2017 9:50 AM, Joel Esler (jesler) wrote:
 The team working on these issues is seeing these emails, so it’s good
>>> that you are writing in, if you are still experiencing issues.
>>> ___
>>> clamav-users mailing list
>>> clamav-users@lists.clamav.net
>>> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>>> 
>>> 
>>> Help us build a comprehensive ClamAV guide:
>>> https://github.com/vrtadmin/clamav-faq
>>> 
>>> http://www.clamav.net/contact.html#ml
>>> 
>> 
>> 
> 
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-09 Thread Adolf Belka 
I am still seeing the message. Periodically it stops and when I check 
that is when the time from the DNS record has become closer to my 
computers time but then the delta progressively increases and exceeds 
the 3 hours and the message starts again. Today it started again at 
10:12 (Netherlands time zone). At 9:56 it was fine.


Here is the DNS TXT value I get:-

current.cvd.clamav.net descriptive text 
"0.99.2:58:24027:1510207861:1:63:46632:318"


My current computer time was 1510221600.

The following came from the dig command:-

; <<>> DiG 9.9.5-3ubuntu0.16-Ubuntu <<>> current.cvd.clamav.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20331
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;current.cvd.clamav.net.        IN    A

;; AUTHORITY SECTION:
cvd.clamav.net.        3600    IN    SOA    ns3.clamav.net. 
hostmaster.oltrelinux.com. 2006375260 1800 900 604800 7200


;; Query time: 281 msec
;; SERVER: 192.168.26.254#53(192.168.26.254)
;; WHEN: Thu Nov 09 11:03:50 CET 2017
;; MSG SIZE  rcvd: 116

Regards,

Adolf Belka

Sent from my Desktop Computer

On 08/11/17 20:47, David Raynor wrote:

The DNS records are being updated at the source properly now. If you are
still seeing an error, then the proper record is not reaching the server
you are contacting for DNS or not propagating correctly to your area or
something like that.

If you are still seeing those errors, let us know what the value of the DNS
TXT record you are seeing for current.cvd.clamav.net. You can use "host" or
"dig" or another command to check it.

Example (with current value):

$ host -t txt current.cvd.clamav.net
current.cvd.clamav.net descriptive text
"0.99.2:58:24025:1510165084:1:63:46630:318"

Dave R.

On Wed, Nov 8, 2017 at 11:34 AM, Noel Jones  wrote:


I'm still getting these errors too.   :\




   -- Noel Jones


On 11/8/2017 9:50 AM, Joel Esler (jesler) wrote:

The team working on these issues is seeing these emails, so it’s good

that you are writing in, if you are still experiencing issues.
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml






___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-08 Thread Jeff 
The last three updates did not have the error. Below is the last error I got:

--
ClamAV update process started at Wed Nov 08 13:13:12 2017
WARNING: DNS record is older than 3 hours.
WARNING: Invalid DNS reply. Falling back to HTTP mode.
securiteinfo.hdb is up to date (version: custom database)
securiteinfo.ign2 is up to date (version: custom database)
javascript.ndb is up to date (version: custom database)
securiteinfohtml.hdb is up to date (version: custom database)
securiteinfoascii.hdb is up to date (version: custom database)
Reading CVD header (main.cvd): nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.us.clamav.net (IP: 128.199.133.36)
Trying host db.us.clamav.net (155.98.64.87)...
OK (IMS)
main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: 
sigmgr)
Can't query main.58.82.1.1.9B624057.ping.clamav.net
Reading CVD header (daily.cvd): OK (IMS)
daily.cld is up to date (version: 24025, sigs: 1774918, f-level: 63, builder: 
neo)
Can't query daily.24025.82.1.1.9B624057.ping.clamav.net
Reading CVD header (bytecode.cvd): OK
bytecode.cld is up to date (version: 318, sigs: 75, f-level: 63, builder: 
raynman)
--

Here's what I got on Windows when I check the TXT record:

...
nslookup -q=txt current.cvd.clamav.net
DNS request timed out.
timeout was 2 seconds.
Server:  UnKnown
Address:  192.168.0.1

Non-authoritative answer:
current.cvd.clamav.net  text =

"0.99.2:58:24025:1510165084:1:63:46630:318"

(root)  nameserver = j.root-servers.net
(root)  nameserver = m.root-servers.net
(root)  nameserver = c.root-servers.net
(root)  nameserver = k.root-servers.net
(root)  nameserver = a.root-servers.net
(root)  nameserver = h.root-servers.net
(root)  nameserver = e.root-servers.net
(root)  nameserver = i.root-servers.net
(root)  nameserver = f.root-servers.net
(root)  nameserver = d.root-servers.net
(root)  nameserver = b.root-servers.net
(root)  nameserver = l.root-servers.net
(root)  nameserver = g.root-servers.net
...

-Original Message-
From: clamav-users [mailto:clamav-users-boun...@lists.clamav.net] On Behalf Of 
David Raynor
Sent: Wednesday, November 08, 2017 2:48 PM
To: ClamAV users ML
Subject: Re: [clamav-users] FreshClam - DNS issues since October 31st

The DNS records are being updated at the source properly now. If you are still 
seeing an error, then the proper record is not reaching the server you are 
contacting for DNS or not propagating correctly to your area or something like 
that.

If you are still seeing those errors, let us know what the value of the DNS TXT 
record you are seeing for current.cvd.clamav.net. You can use "host" or "dig" 
or another command to check it.

Example (with current value):

$ host -t txt current.cvd.clamav.net
current.cvd.clamav.net descriptive text
"0.99.2:58:24025:1510165084:1:63:46630:318"

Dave R.

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-08 Thread Noel Jones 
It's working now.  The last error in the log was about 30 minutes
after the report below.

Thanks.

Location is US central time zone with local DNS resolver FWIW.


  -- Noel Jones



On 11/8/2017 1:47 PM, David Raynor wrote:
> The DNS records are being updated at the source properly now. If you are
> still seeing an error, then the proper record is not reaching the server
> you are contacting for DNS or not propagating correctly to your area or
> something like that.
> 
> If you are still seeing those errors, let us know what the value of the DNS
> TXT record you are seeing for current.cvd.clamav.net. You can use "host" or
> "dig" or another command to check it.
> 
> Example (with current value):
> 
> $ host -t txt current.cvd.clamav.net
> current.cvd.clamav.net descriptive text
> "0.99.2:58:24025:1510165084:1:63:46630:318"
> 
> Dave R.
> 
> On Wed, Nov 8, 2017 at 11:34 AM, Noel Jones  wrote:
> 
>> I'm still getting these errors too.   :\
>>
>>
>>
>>
>>   -- Noel Jones
>>
>>
>> On 11/8/2017 9:50 AM, Joel Esler (jesler) wrote:
>>> The team working on these issues is seeing these emails, so it’s good
>> that you are writing in, if you are still experiencing issues.
>>>
>> ___
>> clamav-users mailing list
>> clamav-users@lists.clamav.net
>> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>>
>>
>> Help us build a comprehensive ClamAV guide:
>> https://github.com/vrtadmin/clamav-faq
>>
>> http://www.clamav.net/contact.html#ml
>>
> 
> 
> 

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-08 Thread David Raynor 
The DNS records are being updated at the source properly now. If you are
still seeing an error, then the proper record is not reaching the server
you are contacting for DNS or not propagating correctly to your area or
something like that.

If you are still seeing those errors, let us know what the value of the DNS
TXT record you are seeing for current.cvd.clamav.net. You can use "host" or
"dig" or another command to check it.

Example (with current value):

$ host -t txt current.cvd.clamav.net
current.cvd.clamav.net descriptive text
"0.99.2:58:24025:1510165084:1:63:46630:318"

Dave R.

On Wed, Nov 8, 2017 at 11:34 AM, Noel Jones  wrote:

> I'm still getting these errors too.   :\
>
>
>
>
>   -- Noel Jones
>
>
> On 11/8/2017 9:50 AM, Joel Esler (jesler) wrote:
> > The team working on these issues is seeing these emails, so it’s good
> that you are writing in, if you are still experiencing issues.
> >
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>



-- 
---
Dave Raynor
Talos Security Intelligence and Research Group
dray...@sourcefire.com
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-08 Thread Noel Jones 
I'm still getting these errors too.   :\




  -- Noel Jones


On 11/8/2017 9:50 AM, Joel Esler (jesler) wrote:
> The team working on these issues is seeing these emails, so it’s good that 
> you are writing in, if you are still experiencing issues.
> 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-08 Thread Joel Esler (jesler) 
The team working on these issues is seeing these emails, so it’s good that you 
are writing in, if you are still experiencing issues.

Sent from my iPad

On Nov 8, 2017, at 9:05 AM, Simon Mousey Smith 
> wrote:

Maybe not every day but every week maybe?

Has the issue been resolved yet?

Simon

On 8 Nov 2017, at 14:02, Reindl Harald 
> wrote:



Am 08.11.2017 um 14:43 schrieb Jeff:
Since October 31st, I get the following DNS warnings every time freshclam
runs:
...
ClamAV update process started at Tue Nov 07 09:26:33 2017
+++WARNING: DNS record is older than 3 hours.+++
+++WARNING: Invalid DNS reply. Falling back to HTTP mode.+++

do we really need each day a new thread about it?
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-08 Thread Simon Mousey Smith 
Maybe not every day but every week maybe?

Has the issue been resolved yet?

Simon

> On 8 Nov 2017, at 14:02, Reindl Harald  wrote:
> 
> 
> 
> Am 08.11.2017 um 14:43 schrieb Jeff:
>> Since October 31st, I get the following DNS warnings every time freshclam
>> runs:
>> ...
>> ClamAV update process started at Tue Nov 07 09:26:33 2017
>> +++WARNING: DNS record is older than 3 hours.+++
>> +++WARNING: Invalid DNS reply. Falling back to HTTP mode.+++
> 
> do we really need each day a new thread about it?
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Re: [clamav-users] FreshClam - DNS issues since October 31st

2017-11-08 Thread Reindl Harald 



Am 08.11.2017 um 14:43 schrieb Jeff:

Since October 31st, I get the following DNS warnings every time freshclam
runs:

...
ClamAV update process started at Tue Nov 07 09:26:33 2017
+++WARNING: DNS record is older than 3 hours.+++
+++WARNING: Invalid DNS reply. Falling back to HTTP mode.+++


do we really need each day a new thread about it?
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml