Secondaries need to 'know' that this old sec is now a master as well.<br><br><span style="font-family:Prelude, Verdana, san-serif;">DNS is kind of critical (unless your internet presence is not important), so ... Knowing nothing about you org... Would rec that you priortise fixing DNS pretty highly.<br><br></span><span id="signature"><div style="font-family: arial, sans-serif; font-size: 12px;color: #999999;"><br>--<br>-___________________________________<br>David Miller<br>Tiggee LLC<br>email@example.com</div><br></span><span style="color:navy; font-family:Prelude, Verdana, san-serif; "><hr align="left" style="width:75%">On May 6, 2010 23:23, Barry Margolin <firstname.lastname@example.org> wrote: <br><br>In article <email@example.com>,
<br> Bruce Ray <Bruce.Ray@zionsbancorp.com> wrote:
<br>> You have until the expiry counter expires for a given zone.
<br>> We typically run our expiries at a week to allow for this type of failure.
<br>You can easily turn a slave into a master. Just go into its named.conf
<br>file, change "type slave" to "type master" and comment out the "masters
<br>> From: firstname.lastname@example.org
<br>> To: email@example.com <firstname.lastname@example.org>
<br>> Sent: Thu May 06 21:37:35 2010
<br>> Subject: Master server offline
<br>> Our master server machine had a drive failure and looks like it will be
<br>> offline for some time. Somewhere in the back of my mind, I thought I
<br>> remembered that something bad can happen to the dns resolution for your zones
<br>> if the master is offline for too long. Is there anything to this or am I just
<br>> dreaming? As long as the secondary can answer request, we should be ok?
<br>Barry Margolin, email@example.com
<br>*** PLEASE don't copy me on replies, I'll read them in the group ***
<br>bind-users mailing list