Maintain task frequency

Jorge Alberto Martínez Melo jorge.martinez at
Tue May 10 15:09:09 UTC 2016

Thank you both, rob0 and Barry, very usefull notes.

It seems that my maintain proposed tasks are unnecessary. Furthermore
occasional backups and updates, in your opinion what are frequent
necessary maintain tasks for a cache dns server.

Thank you in advance for your comments

-- jamm

On 09/05/16 20:34, Barry S. Finkel wrote:
> On Mon, 9 May 2016 17:54:22 -0500, Jorge Alberto Mart?nez Melo
> <jorge.martinez at> wrote:
>> Hello bind users,
>> I am preparing some scripts to maintain some cache dns servers and I am
>> thinking about the most appropriate frequency of these tasks:
>> - to generate the root hints file (root cache).
>> - to clear the cache with rndc flush
>> - to generate the stats file with rndc stat
>> Thank you in advance for your comments
>> -- jamm
> If I interpret your question correctly - here are my answers:
> 1) root hints - There is nothing you need to do, as BIMD will get
>                 the information when it starts, based on the hints
>                 that are built into the code.  And the hints information
>                 rarely changes.
> 2) Clear cache - There is no need to clear the cache, as BIND will
>                  remove automatically any entry whose TTL has
>                  expired.
> 3) Generating stets - I have no answer for this.  You can generate
>                       stats at any interval you want.  The interval
>                       might depend upon  how busy the DNS server is.
> --Barry Finkel
> _______________________________________________
> Please visit to
> unsubscribe from this list
> bind-users mailing list
> bind-users at

Aviso de Privacidad:

Este correo electrónico, incluyendo en su caso, los archivos adjuntos al
mismo, pueden contener informacion de carácter confidencial y/o
privilegiada, y se envian a la atención única y exclusivamente de la persona
y/o entidad a quien va dirigido. La copia, revisión, uso, revelación y/o
distribución de dicha informacion confidencial sin la autorización por escrito
de Triara está prohibida. Si usted no es el destinatario a quien se dirige el
presente correo, favor de contactar al remitente respondiendo al presente
correo y eliminar el correo original incluyendo sus archivos, asi como
cualesquiera copia del mismo. Mediante la recepción del presente correo
usted reconoce y acepta que en caso de incumplimiento de su parte y/o de
sus representantes a los términos antes mencionados, Triara tendrá
derecho a los daños y perjuicios que esto le cause.

This e-mail message including attachments, if any, is intended only for the
person or entity to which it is addressed and may contain confidential and
/or privileged material. Any review, use, disclosure or distribution of such
confidential information without the written authorization of Triara is
prohibited. If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies of the original message. By receiving
this e-mail you acknowledge that any breach by you and/or your
representatives of the above provisions may entitle Triara to seek for

05/10/16 10:08:46

More information about the bind-users mailing list