A way to prevent this from happening may be to choose the "expire" time in the SOA more carefully:
The zone expiry time should be set to cover the span of time which a secondary can reliably serve a zone in the absence of a responsive master.
It's fairly obvious that a secondary, in the absence of a responsive master, can only operate until the signatures expire.
Problem: the expiry time is relative to the last time the zone is refreshed, the signatures expire at an absolute time. Hmmm.
Okay, I don't have a quick answer here. Rats.
But don't link the two clocks together. Expiry is relative, needs no synchronized time source. Expiration is absolute, needs a coordinated time.
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis +1-703-227-9854 ARIN Research Engineer
#---------------------------------------------------------------------- # To unsubscribe, send a message to <[EMAIL PROTECTED]>.
