We have the zone data - the slave is alive and the zones are on disk. I don't care about recovering the master server that died because we've been wanting to move the zones it served to our Infoblox systems anyways and this presented a 'do or die' opportunity. The original question was to determine how much time we had to do so.
Besides, whoever said this was production and that our Infoblox infrastructure wasn't already vetted? -----Original Message----- From: Chuck Swiger [mailto:cswi...@mac.com] Sent: Wednesday, November 16, 2011 10:33 PM To: Hajducko, Steven Cc: bind-users@lists.isc.org Subject: Re: Query zone expiration time On Nov 16, 2011, at 10:20 PM, Hajducko, Steven wrote: > Yeah, that's if we wanted to bother recovering it. :) Then there is the process of recovering the master conf file and setting up notifies and allows for all the slaves the old master had. Hmm. If you don't care about recovering the zone data, why were you bothering to serve it in the first place? > We're actually going to move the zones to our Infoblox system, which is why we wanted to determine if we had enough time or if we had to bother with the recovery, hence the question. If I had a transition already planned and implemented, and the replacement system was adequately tested to the point where I was willing to switch over early due to an unexpected system failure, then I might consider switching a production system over to something else. The other 99% of the time, if something in production breaks, you replace it with exactly the same thing. Making any kind of infrastructure change is handled in a process which is not emergency recovery from a failure. Regards, -- -Chuck _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
