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
