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

mmin...@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

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

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@l

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

--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 pr

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

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

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

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

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. >

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

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

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

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: >> ...

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

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