X-zuka-RWMailScanner-ID: 063F2638001.AC137
X-zuka-rw-MailScanner-Information: Please contact the ISP for more information
Received: from Magnolia.local (unknown [70.48.209.168])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
(Authenticated sender: [email protected])
by rosewood.zuka.net (Postfix) with ESMTP id 063F2638001
for <[email protected]>; Thu, 6 May 2010 23:23:23 -0400 (EDT)
Message-ID: <[email protected]>
Date: Thu, 06 May 2010 23:22:09 -0400
From: Dave Filchak <[email protected]>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: [email protected]
Subject: Re: Master server offline
References: <[email protected]>
<[email protected]>
In-Reply-To: <[email protected]>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mx.pao1.isc.org
X-BeenThere: [email protected]
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: BIND Users Mailing List <bind-users.lists.isc.org>
List-Unsubscribe: <https://lists.isc.org/mailman/options/bind-users>,
<mailto:[email protected]?subject=unsubscribe>
List-Archive: <https://lists.isc.org/pipermail/bind-users>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[email protected]?subject=help>
List-Subscribe: <https://lists.isc.org/mailman/listinfo/bind-users>,
<mailto:[email protected]?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8099937040315822544=="
Sender: [email protected]
Errors-To: [email protected]
X-pstn-neptune: 1/1/1.00/81
X-pstn-levels: (S:99.90000/99.90000 CV:99.9000 FC:95.5390 LC:95.5390
R:95.9108 P:95.9108 M:97.0282 C:98.6951 )
X-pstn-settings: 4 (1.5000:1.5000) s cv gt3 gt2 gt1 r p m c
X-pstn-addresses: from <[email protected]> [294/10]
This is a multi-part message in MIME format.
--===============8099937040315822544==
Content-Type: multipart/alternative;
boundary="------------080001040208080201060908"
This is a multi-part message in MIME format.
--------------080001040208080201060908
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
I was thinking that as well ... would probably be the easiest and then
switch it back later. However, I would have to change my glue record at
the registrar as well ... no?
On 06/05/10 11:19 PM, Barry Margolin wrote:
> In article<[email protected]>,
> Bruce Ray<[email protected]> wrote:
>
>
>> You have until the expiry counter expires for a given zone.
>>
>> We typically run our expiries at a week to allow for this type of failure.
>>
> You can easily turn a slave into a master. Just go into its named.conf
> file, change "type slave" to "type master" and comment out the "masters
> {...}" clause.
>
>
>> ________________________________
>> From: [email protected]
>> <[email protected]>
>> To: [email protected]<[email protected]>
>> Sent: Thu May 06 21:37:35 2010
>> Subject: Master server offline
>>
>> Our master server machine had a drive failure and looks like it will be
>> offline for some time. Somewhere in the back of my mind, I thought I
>> remembered that something bad can happen to the dns resolution for your zones
>> if the master is offline for too long. Is there anything to this or am I just
>> dreaming? As long as the secondary can answer request, we should be ok?
>>
>> Cheers,
>>
>> Dave
>>
>
--------------080001040208080201060908
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#333333">
<font face="Helvetica, Arial, sans-serif">I was thinking that as well
... would probably be the easiest and then switch it back later.
However, I would have to change my glue record at the registrar as well
... no?</font><br>
<br>
On 06/05/10 11:19 PM, Barry Margolin wrote:
<blockquote
cite="mid:[email protected]"
type="cite">
<pre wrap="">In article <a class="moz-txt-link-rfc2396E"
href="mailto:[email protected]";><[email protected]></a>,
Bruce Ray <a class="moz-txt-link-rfc2396E"
href="mailto:[email protected]";><[email protected]></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">You have until the expiry counter expires for a given zone.
We typically run our expiries at a week to allow for this type of failure.
</pre>
</blockquote>
<pre wrap="">
You can easily turn a slave into a master. Just go into its named.conf
file, change "type slave" to "type master" and comment out the "masters
{...}" clause.
</pre>
<blockquote type="cite">
<pre wrap="">
________________________________
From: <a class="moz-txt-link-abbreviated"
href="mailto:[email protected]";>[email protected]</a>
<a class="moz-txt-link-rfc2396E"
href="mailto:[email protected]";><[email protected]></a>
To: <a class="moz-txt-link-abbreviated"
href="mailto:[email protected]";>[email protected]</a> <a
class="moz-txt-link-rfc2396E"
href="mailto:[email protected]";><[email protected]></a>
Sent: Thu May 06 21:37:35 2010
Subject: Master server offline
Our master server machine had a drive failure and looks like it will be
offline for some time. Somewhere in the back of my mind, I thought I
remembered that something bad can happen to the dns resolution for your zones
if the master is offline for too long. Is there anything to this or am I just
dreaming? As long as the secondary can answer request, we should be ok?
Cheers,
Dave
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
</body>
</html>
--------------080001040208080201060908--
--===============8099937040315822544==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users
--===============8099937040315822544==--
