controlling size of jnl file for dynamic updates

[Jeff Synnestvedt]

I recently have picked BIND to use as a dns server in a project I am
doing. To keep it brief I end up sending a lot of ddns updates to
bind because this project involves a lot of IPs that are constantly
changing.

So far tests have shown that BIND is working very well and handling
all the updates fine. The only problem I have uncovered is with the
size of the jnl file. Over time after many updates the jnl file grows
to a substantial size (right now after some initial testing it is
already at the 500MB mark). I have onlly found one way to reduce the
size of the file and that is to stop the server, remove the file and
the start the server again. This works because when you stop BIND it
writes all of the jnl entries into the zone file.

Is there any configuration or other way I can limit the size or
truncate this file? It is very critical that this server remain up
and even taking it down for the breif period of time to remove the jnl
file is very undesireable right now.

Thanks,

-Jeff

[Mark Andrews]

Post by Jeff Synnestvedt
I recently have picked BIND to use as a dns server in a project I am
doing. To keep it brief I end up sending a lot of ddns updates to
bind because this project involves a lot of IPs that are constantly
changing.
So far tests have shown that BIND is working very well and handling
all the updates fine. The only problem I have uncovered is with the
size of the jnl file. Over time after many updates the jnl file grows
to a substantial size (right now after some initial testing it is
already at the 500MB mark). I have onlly found one way to reduce the
size of the file and that is to stop the server, remove the file and
the start the server again. This works because when you stop BIND it
writes all of the jnl entries into the zone file.
Is there any configuration or other way I can limit the size or
truncate this file? It is very critical that this server remain up
and even taking it down for the breif period of time to remove the jnl
file is very undesireable right now.
Thanks,
-Jeff

Upgrade to 9.3 and use max-journal-size.

zone "example.net" {
...
max-journal-size #;
};
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: [phone] INTERNET: ***@isc.org

[Planet X Mail]

Hello,

I too have the same problem. I run BIND 9.2.3

Is there a configuration I can use that will limit the size of the jnl files
for ALL zones in just one config command INSTEAD of having to hhave it
specified for each and every zone?

If so, what are the specifics on it... also keep in mind Im running BIND 9.2.3

Thanks in advance,
-matt

Post by Mark Andrews

Post by Jeff Synnestvedt
I recently have picked BIND to use as a dns server in a project I am
doing. To keep it brief I end up sending a lot of ddns updates to
bind because this project involves a lot of IPs that are constantly
changing.
So far tests have shown that BIND is working very well and handling
all the updates fine. The only problem I have uncovered is with the
size of the jnl file. Over time after many updates the jnl file grows
to a substantial size (right now after some initial testing it is
already at the 500MB mark). I have onlly found one way to reduce the
size of the file and that is to stop the server, remove the file and
the start the server again. This works because when you stop BIND it
writes all of the jnl entries into the zone file.
Is there any configuration or other way I can limit the size or
truncate this file? It is very critical that this server remain up
and even taking it down for the breif period of time to remove the jnl
file is very undesireable right now.
Thanks,
-Jeff

Upgrade to 9.3 and use max-journal-size.
zone "example.net" {
...
max-journal-size #;
};
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia