Journal problem (jnl files)

[SilentRage]

Never heard of journalprint, but I do know that BIND 9.3.0 introduced a feature in named-checkzone to print the zone from the journal if it exists.  It's probably my second favorite feature with rndc freeze/thaw barely making first.

But yeah, as I said, it is NOT a problem that the zone file isn't being dumped to.  The zone file is not even being read anymore unless you remove that jnl file.  I suggest that you run these two commands replacing paths and zone name appropriately:

named-checkzone -qD domain.tld "/var/named/domain.tld.zone"
named-checkzone -jqD domain.tld "/var/named/domain.tld.zone"

The first command prints the zone file.  The second command prints the journal file.  See if they're identical.  This might not actually teach us anything new about the problem, but it's a nice thing to look at.  I can't explain why the zone file isn't being dumped to 15 minutes after the last update.  You could confirm this is the case by checking this:

# ls -la /var/named/domain.tld.jnl
# date

Make sure the last time the journal was updated was over 15 minutes ago.  I think I'll go check the BIND 9.3.0 manual about this.  The last time I read the 15 minute thing was when I had BIND 9.2.3.

Dave

--- Reply to: Stefan Puiu <stefanpuiu at itcnetworks.ro> ---
> 
> 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!
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>      
> >>>
> >>    
> >>
> >
> >
> >
> >  
> >
> 
> 
> 
>