The Question is:
Our installation of TCP/IP (V5.3 - ECO 1) uses the supplied BIND parameters. We
have noticed that the BIND database version is slowly kreeping upwards and
that new journal files are being created. what causes this and if possible can
I configure it deffie
The Answer is :
Please see the discussion of the BIND journal file processing in
the TCP/IP Services V5.3 release notes for details on this.
If this file becomes a particular concern, you can reset with:
1: rndc flush-updates
2: shut down the bind server
3: remove the zone's _JNL file
4: restart the server
An update to the behaviour of the BIND Journal file processing is
under consideration for inclusion in a release after V5.3.