nsupdate question

James Hall-Kenney JHall at sytec.co.nz
Wed Nov 10 23:23:42 UTC 1999

Previous reply from Cricket Liu:

"That's basically right.  The .log file is BIND's way of "journaling"
updates to the zone.  Each time BIND receives a dynamic update, it writes a
record of the update to the .log file.  Roughly each hour, it should rewrite
the whole zone data file from its in-memory copy of the zone and delete the
.log file.  This is a Good Thing because BIND doesn't have to rewrite a
potentially very large zone data file each time it gets a dynamic update,
yet it commits a record of the dynamic update to stable storage so it won't
be lost if BIND crashes.  When BIND starts, of course, it aggregates any
.log file into the current zone.

The .ixfr file is yet another record of changes to the zone, but in this
case for incremental zone transfers.  BIND master name servers keep a record
of the changes between one serial number and the next, so that when a slave
requests the delta between serial 1999083000 and 1999083002, it can provide


-----Original Message-----
From: Steve WANG [mailto:xwang4 at gmu.edu]
Sent: Thursday, 11 November 1999 10:04
To: bind-users at isc.org
Subject: nsupdate question

Hi, all,

We are using the BIND822 on Windows NT. I configured it to let it be
dynamically updateable.

Then I ran the nsupdate to add a RR. I could see the result by using
nslookup to query the server. 

However, when I checked the server configuration I found that the dynamic
update is NOT merged into the master file. Instead the update information
is in a log file (*.log) and ixfr file.

I just wonder why the named does not update the master file automatically.

Thank you.


More information about the bind-users mailing list