> On Tue, 29 Mar 2011 10:52:49 -0700, Kevin Oberman wrote > > The relevant field in the SOA is the "expire' field. If the server > > has either transferred the zone from the master server or confirmed (via > > serial #) that the current data is still current. If the data is > > expired, the slave will stop serving it. Until then, it will serve it > > and TTL has absolutely nothing to do with this.
On 29.03.11 12:07, listmail wrote: > So is this correct: A slave will continue serving RRs regardless of their TTL, > as long as the "expire" value in the SOA has not expired? > > If true, I need another theory as to why the slave stopped serving records. The slave periodically checks (interval defined by SOA refresh/retry values) if the data are still fresh. If the data can't be verified for expire seconds, the zone is dropped. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Emacs is a complicated operating system without good text editor. _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
