I lied. The DNS server order in resolv.cfg was wrong. The external DNS servers were supposed to be first.
Sorry for wasting time. ----- Original Message ---- From: Sean McGlynn <[EMAIL PROTECTED]> To: clamav-users@lists.clamav.net Sent: Tuesday, October 30, 2007 10:01:17 AM Subject: [Clamav-users] Freshclam Stopped Working Hello, After changing our DNS services from Netware to OES Linux/BIND, freshclam stopped getting updates. When we run freshclam we get: WARNING: Can't query current.cvd.clamav.net and WARNING: Invalid DNS reply. Falling back to HTTP mode. Connecting via Our_proxy_server_IP Reading CVD header (main.cvd): ERROR: Unknown response from remote server WARNING: Can't read main.cvd header from db.us.rr.clamav.net (IP: Our_proxy_server_IP) Using nslookup on our proxy server (which is Netware 6.5) I get valid responses for both current.cvd.clamav.net and db.us.clamav.net. Our firewall log is showing the proxy server attempting to contact our internal DNS server at the times freshclam is running, so it appears the proxy server is trying to resolve the names via our internal DNS server rather than our external (Internet) DNS servers. resolv.cfg has our internal DNS server first in the list, but that has always been. Can anyone suggest a resolution? Thank you. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
