Hello bind-users, Tried to find the info on my own but couldn’t get accurate understanding of jnl files flushing mechanism.
Bind-9.10.0-02.P2 RHEL 5.7 Master DNS server, Chrooted env, receiving updates via nsupdate. Maybe I didn’t catch the memo but I thought the standard way bind handled the dynamic journal (.jnl) files was this way: All changes made to a zone using dynamic update are written to the zone's journal file. The server will periodically flush the complete contents of the updated zone to its zone file this happens approximately every 15 minutes. NOTE this is from zytrax.com dns documentation so I’m pretty sure this is not from bind 9.10 Doesn’t seem to be the case right now and I’m wondering if my server conf is to blame. I’m able to sync to flat files using rndc: rndc sync –clean That I see in my logs: named[3001]: received control channel command 'sync -clean' named[3001]: dumping all zones, removing journal files: success But the next day I’m seeing tons of jnl files again. From updates of course. I do have these journal messages in my logs: general: debug 1: zone XX.128.in-addr.arpa/IN: journal rollforward completed successfully: no journal general: debug 3: no journal file, but that's OK general: debug 1: zone XX.XX.10.in-addr.arpa/IN: journal rollforward completed successfully: no journal general: debug 3: no journal file, but that's OK general: debug 1: zone XX.XX.10.in-addr.arpa/IN: journal rollforward completed successfully: no journal general: debug 3: no journal file, but that's OK general: debug 1: zone XX.168.192.in-addr.arpa/IN: journal rollforward completed successfully: no journal So it it does seem to be rolling the changes but jnl files still persist. It’s not terribly bothering but I would like to know if this is the normal behavior. I do not have dnssec-enable of managed-keys-directory set in named.conf Thanks for your help. E. Berthiaume ************************************************************** Ce courrier électronique, y compris les pièces jointes, est à l'attention exclusive des destinataires désignés et revêt un caractère confidentiel. Si vous recevez ce courrier électronique par erreur, merci d'en informer sans délai l'expéditeur et de supprimer son contenu et ses pièces jointes. Le contenu de ce courrier électronique ne pourrait engager la responsabilité de la Banque de France que s'il a été émis par une personne dûment habilitée agissant dans le strict cadre des fonctions auxquelles elle est employée et à des fins non étrangères à ses attributions. L'expéditeur de ce courrier électronique ne peut pas garantir la sécurité de l'acheminement par voie électronique et ne saurait dès lors encourir une quelconque responsabilité en cas d'altération de son contenu. ************************************************************** This e-mail, attachments included, is intended solely for the addressees and should be considered as confidential. Should you receive this message by error, please notify the sender immediately and destroy this e-mail and its attachments. Banque de France cannot be considered as liable for the content of this message unless the sender has been duly authorized and has acted strictly in the course of his/her tasks as an employee. The sender of this e-mail cannot ensure the security of its electronic transmission and consequently will not be liable should its content be altered. **************************************************************
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
