Journal problem (jnl files)

Stefan Puiu stefanpuiu at itcnetworks.ro
Thu Nov 11 15:09:15 UTC 2004


Not sure about BIND 9.3.0, but for 9.2.3 the ARM says the zones have to 
be dumped every 15 minutes, as you implied.

Does the zone load properly? If the rollforward of a journal file fails 
for a zone, BIND 9.2.3 won't be able to properly serve that zone (look 
for zone rollforward errors in your logs). Do you usually edit your zone 
files manually? In 9.3, I think you're supposed to run 'rndc freeze' (?) 
in order to block updates for the zone you're editing, change the zone 
and then do a 'rndc thaw'.

You can check the journal contents with 'journalprint' from the BIND 9 
source (in bin/tests). You might want to check the SOA serials in the 
journal and the one in the zone file - if the zone file serial in 
bigger, you'd have problems (in BIND 9.2 at least).

Bind Mailing List wrote:

>We don't receive updates rather frequently. I realy don't know why zones are
>not updated evrey 15 minutes.
>
>Any other ideas?
>
>----- Original Message ----- 
>From: <bind9-users at isc.org>
>To: "Bind Mailing List" <bind_ml36 at telusquebec.net>
>Sent: Wednesday, November 10, 2004 4:30 PM
>Subject: Re: Journal problem (jnl files)
>
>
>  
>
>>Well, this isn't a problem.  BIND reads from the jnl file if you should
>>    
>>
>restart it.  But I do find it strange that the zone file hasn't been
>updated.  Perhaps it's cause you recieve updates rather frequently?  As far
>as I know, BIND dumps the jnl file to text format in the zone file after 15
>minutes since the last update.
>  
>
>>Dave
>>
>>--- Reply to: Bind Mailing List <bind_ml36 at telusquebec.net> ---
>>    
>>
>>>Need help!
>>>We use bind 9.3.0 on Solaris 8. We have some problems with the journal
>>>fonctionality.
>>>Regularly we can find some old zone files in /etc/named even if the
>>>jnl files are up to date on our server.
>>>
>>>Here an example:
>>>-rw-r--r--   1 root     sys         2365 Nov  3 15:18
>>>domainexample.com
>>>-rw-r--r--   1 root     sys          812 Nov 10 14:45
>>>domainexample.com.jnl
>>>
>>>In this example, the domain is 7 days old and the jnl is up to date.
>>>The refresh time of this zones is 15 minutes.
>>>
>>>Is-that normal?
>>>If not, how can we fix it?
>>>
>>>We are effraid about losing some updates.
>>>
>>>Waiting for you answer!
>>>Thanks a lot!
>>>
>>>
>>>
>>>
>>>
>>>      
>>>
>>    
>>
>
>
>
>  
>



More information about the bind-users mailing list