We temporarily bumped the TTL up to three hours yesterday to ease the burden on the mirrors while we pushed out a change that would cause a lot of bandwidth. The TTL will be set back to its previous value soon.
On Fri, Feb 15, 2013 at 7:26 AM, Kees Theunissen <c.j.theunis...@differ.nl>wrote: > The "ClamAV Virus Databases" FAQ > (http://www.clamav.net/lang/en/faq/faq-cvd/) says: > > You can check for database update as often as 4 times per hour > provided that you have the following options in freshclam.conf: > DNSDatabaseInfo current.cvd.clamav.net > DatabaseMirror db.XY.clamav.net > DatabaseMirror database.clamav.net > Replace XY with your country code. If you don't have that option, > then you must stick with 1 check per hour. > > But the TTL (Time To Live) on the current.cvd.clamav.net TXT > Resource Record is 10800 seconds (3 hours). > > ~$ dig @ns3.clamav.net txt current.cvd.clamav.net > [...] > ;; ANSWER SECTION: > current.cvd.clamav.net. 10800 IN TXT > "0.97.6:54:16685:1360928385:0:63:40236:214" > [...] > > > This will cause the record to be kept in DNS caches for 3 hours > and it will reduce the effective update frequency to once in > 3 hours (unless you can flush your resolver casches). > Shouldn't the TTL be reduceced to something like 900 seconds? > > > Regards, > > Kees Theunissen. > > -- > Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 > Dutch Institute For Fundamental Energy Research (DIFFER) > e-mail address: c.j.theunis...@differ.nl > postal address: PO Box 1207, 3430 BE Nieuwegein, NL > visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL > > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://www.clamav.net/support/ml > _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
