BIND 8.2.3 and serial 0/slave server question

[David R. Kirk]

This function then, as documented in O'Reilly' s DNS & BIND (3rd
Edition) was a bug in the BIND code?

That is disappointing.  The 0 ("zero") serial number had always
provided the means, save for data errors, for zones to be pulled from
the master by a slave server; it certainly allowed us to provide a
reasonably quick issue resolution for those folks that ended up with
out-of-bounds serial numbers or made zone changes that they needed
to guarantee would be picked up ASAP by their slaves.

Thanks for the information.  We'll move forward with that knowledge.

- dave


> It was a bug.  Bugs get fixed.  Please teach them how to
> rollover the serical number in future as that works with
> all but really old BIND 4 slaves.
>
> > Does the old trick, that worked up at least up through BIND 8.1.2, of
> > setting the zone serial number to 0 ("zero") to force a pull from slave
> > servers still work?
> >
> > We are providing slave service for a number of our customers, and we
> > have always told them to set the serial number to 0 ("zero") when they
> > mucked up their zone files and needed to bring sanity back to their
> > zones before we could slave the zones.  However, of late, it seems that
> > this function is not working, or possibly not working in the same way
> > it once did.  Has anyone else seen this?  Am I totally off-base?  Am I
> > not waiting long enough for the slave servers to pick up the zones
> > (though I have waited ~6 hours for one of the zones to be slaved)?
> >
> > Any assistance/insight that anyone can offer would be greatly
appreciated.