[Clamav-users] Warning while update
Hi everybody, Im having the next warning on freshclam.log file all updates I launch ARNING: Invalid DNS reply. Falling back to HTTP mode. main.cvd is up to date (version: 38, sigs: 51206, f-level: 7, builder: tkojm) daily.cvd is up to date (version: 1479, sigs: 5261, f-level: 8, builder: ccordes) -- -- freshclam daemon 0.88.2 (OS: linux-gnu, ARCH: i386, CPU: i386) ClamAV update process started at Wed May 24 18:40:39 2006 WARNING: DNS record is older than 3 hours. WARNING: Invalid DNS reply. Falling back to HTTP mode. main.cvd is up to date (version: 38, sigs: 51206, f-level: 7, builder: tkojm) daily.cvd is up to date (version: 1479, sigs: 5261, f-level: 8, builder: ccordes) -- -- freshclam daemon 0.88.2 (OS: linux-gnu, ARCH: i386, CPU: i386) ClamAV update process started at Wed May 24 18:52:12 2006 WARNING: DNS record is older than 3 hours. WARNING: Invalid DNS reply. Falling back to HTTP mode. main.cvd is up to date (version: 38, sigs: 51206, f-level: 7, builder: tkojm) daily.cvd is up to date (version: 1479, sigs: 5261, f-level: 8, builder: ccordes) -- Im quite worried about that because in FAQ tells if it happens only once to ignore it but when it happens often what should I do? I use my isp dns servers so no dns caching or something like that Please ask me this a proxy smtp production server Thank you Egoitz Aurrekoetxea Dpto.técnico Infobiok C.B. 94 - 674 37 21 ___ http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] Warning while update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, May 24, 2006 at 11:33:31AM +0200, Egoitz Aurrekoetxea wrote: Im quite worried about that because in FAQ tells if it happens only once to ignore it but when it happens often what should I do? I use my isp dns servers so no dns caching or something like that One of two things is probably happening: 1) The particular DNS server this DNS request is going to has stale information. For example, the process that transfers the zone information is failing or is being blocked. There is nothing that you can do about this particular case. 2) Your ISP is cacheing the replies for a period of time longer than the zone record says it should be. Non-compliant DNS servers do this, I have no way of knowing what DNS server your ISP runs. Again, there is nothing that you can do about this particular case. If you want to fix this, you need to experiment and try a few things: 1) Use a different name server than your ISP's. 2) Run a local caching-only name server. By default it will go to the root servers instead of through your ISP's name servers. Just make sure to change /etc/resolv.conf so that it uses 127.0.0.1 instead of your ISP's name servers. Good luck! - -- Regards... Todd We should not be building surveillance technology into standards. Law enforcement was not supposed to be easy. Where it is easy, it's called a police state. -- Jeff Schiller on NANOG Linux kernel 2.6.12-18mdksmp 2 users, load average: 0.09, 0.12, 0.11 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEdMAjY2VBGxIDMLwRAsMwAJ9m1oBlNB1JhPeehXvv0QhEGmKmiwCghWiH v1S2ojfEx+1PM0eimhrfodA= =axvj -END PGP SIGNATURE- ___ http://lurker.clamav.net/list/clamav-users.html
