> > On 01.10.08 22:03, Barry Margolin wrote: > > > Maybe what he's really planning on doing is listing two masters: the > > > real master and itself. Pointing to the real master causes updates to > > > propagate, pointing to itself prevents expiration. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> In article <[EMAIL PROTECTED]>, > Matus UHLAR - fantomas <[EMAIL PROTECTED]> wrote: > > Does it? I'd expect that expiration status only depends on setting in > > named's config, not content of the SOA record. > On 02.10.08 16:23, Barry Margolin wrote: > There's no expiration setting in the named.conf. Expiration depends on > the EXPIRE field of the SOA record, and occurs if the slave is unable to > query the master for the SOA record for that length of time. If the > master is itself, these SOA queries should always succeed, so the zone > won't expire. but why should named think the zone is master and should not be expires, when the config clearly says it's slave? I doubt bind would trust SOA that much... -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; 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. They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin, 1759
