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 <njo...@megan.vbhcs.org> 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
