see max-journal-size ;
In message , Nicholas F Mill
er writes:
> We have a few dynamic zones that are provisioned using Addhost. When
> addhost adds records to the zone every night it will run "nsupdate <
> update.file". The update.file will contain records like these:
>
> prereq yxr
On Wed, 7 Jan 2009, Mike Eggleston wrote:
> On Wed, 07 Jan 2009, Nicholas F Miller might have said:
>
> > We have a few dynamic zones that are provisioned using Addhost. When
> > addhost adds records to the zone every night it will run "nsupdate <
> > update.file". The update.file will contai
All good suggestions. We have given them both some thought. I was just
wondering if there was a problem with the way we were doing things.
Nicholas Miller, ITS, University of Colorado at Boulder
On Jan 7, 2009, at 11:34 AM, Mike Eggleston
I've seen similar behaviors in earlier versions of BIND as well. Since
it doesn't seam to impact performance etc I haven't really bothered
with it. What you can do is to run an rndc freeze/thaw, this will
check out the journal file.
/Jonathan
On Wed, Jan 7, 2009 at 10:30 AM, Nicholas F Miller
wr
On Wed, 07 Jan 2009, Nicholas F Miller might have said:
> We have a few dynamic zones that are provisioned using Addhost. When
> addhost adds records to the zone every night it will run "nsupdate <
> update.file". The update.file will contain records like these:
>
> prereq yxrrset machine.col
Nicholas F Miller wrote:
> We have a few dynamic zones that are provisioned using Addhost. When
> addhost adds records to the zone every night it will run "nsupdate <
> update.file". The update.file will contain records like these:
>
> prereq yxrrset machine.colorado.edu. in a
> update delete mac
We have a few dynamic zones that are provisioned using Addhost. When
addhost adds records to the zone every night it will run "nsupdate <
update.file". The update.file will contain records like these:
prereq yxrrset machine.colorado.edu. in a
update delete machine.colorado.edu. in a
prereq
7 matches
Mail list logo
