<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: Query zone expiration time</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>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.<BR>
<BR>
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.<BR>
<BR>
-----Original Message-----<BR>
From: bind-users-bounces+steven.hajducko=digitalinsight.com@lists.isc.org on behalf of Alan Clegg<BR>
Sent: Wed 11/16/2011 7:34 PM<BR>
To: bind-users@lists.isc.org<BR>
Subject: Re: Query zone expiration time<BR>
<BR>
On 11/16/2011 5:11 PM, Hajducko, Steven wrote:<BR>
<BR>
> We had a master die and we've been meaning to move it off to a newer<BR>
> system. We're trying to determine how much time is left on the zones in<BR>
> order to see if we can do it right or if we have to quickly recover the<BR>
> master.<BR>
<BR>
Change the "type slave" to "type master" and comment out the "masters".<BR>
<BR>
Then "rndc reconfig"<BR>
<BR>
(assuming that the zone is written to disk).<BR>
<BR>
If not, do a "dig zone axfr" and save the output to a file, THEN do the<BR>
above (while adding a "file" statement).<BR>
<BR>
AlanC<BR>
--<BR>
alan@clegg.com | aclegg@infoblox.com<BR>
1.919.355.8851<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>