Zone transfer doesn't work when I set allow-update statement

/dev/rob0 rob0 at
Tue Apr 29 13:08:15 UTC 2014

On Tue, Apr 29, 2014 at 09:50:11AM -0300, Jeronimo L. Cabral wrote:
> Please the last question: can I dynamically update a zone and
> -when necessary- make a freeze, manually add/delete records, and
> after that make a thaw to continue with the dynamic update????
> In other words, a mix betwwen dynamic and manually update.

That's precisely what freeze/thaw is for.

Do note, however, that you lose the zone's history (which is 
necessary for IXFR, and perhaps a matter of interest otherwise)
when you do this. My suggestion is that you learn to be more
comfortable with nsupdate procedures, and stop using freeze/thaw.

> On Fri, Apr 25, 2014 at 6:04 PM, Evan Hunt <each at> wrote:
> > On Fri, Apr 25, 2014 at 05:29:30PM -0300, Jeronimo L. Cabral 
> > wrote:
> > > But the master zone is not refreshed until I execute
> > > "service bind9 restart" ("service bind9 reload" doesn't
> > > refresh the master zone).
> >
> > The zone has been updated, but the changes are stored in a 
> > journal file ("zonefile.jnl").  You can look at the contents
> > of the journal file with "named-journalprint <filename>".
> >
> > If you want to dump the current version of the zone to disk so 
> > you can look at the whole thing, use "rndc sync <zonename>".
> >
> > (That's assuming this is a fairly recent BIND.  If it doesn't 
> > support sync, use "rndc freeze <zone>; rndc thaw <zone>".)
  Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:

More information about the bind-users mailing list