In article mailman.1415.1273200624.21153.bind-us...@lists.isc.org,
Bruce Ray bruce@zionsbancorp.com 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.
Make them 10 days - that way you can break
On May 7 2010, Peter Laws wrote:
On 05/07/10 06:49, Chris Thompson wrote:
Sure - just step into your time machine, go back to before the master
server died, and increase the SOA.expire value there so that it gets
propagated to the slave(s) in time.
If he has a small number of slaves, the OP
On May 7 2010, Dave Filchak wrote:
Well, my SOA Expires are set to 604800 (1 week ). Can I change those to
four weeks to give us some time.
Sure - just step into your time machine, go back to before the master
server died, and increase the SOA.expire value there so that it gets
propagated to
On 05/07/10 06:49, Chris Thompson wrote:
Sure - just step into your time machine, go back to before the master
server died, and increase the SOA.expire value there so that it gets
propagated to the slave(s) in time.
If he has a small number of slaves, the OP may not need a Tardis. It's
In article mailman.1428.1273241309.21153.bind-us...@lists.isc.org,
Peter Laws pl...@ou.edu wrote:
On 05/07/10 06:49, Chris Thompson wrote:
Sure - just step into your time machine, go back to before the master
server died, and increase the SOA.expire value there so that it gets
To: bind-users@lists.isc.org bind-users@lists.isc.org
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
Actually speaking without thinking is bad.
It's the expire timer in the SOA not the refresh.
On Thu, May 6, 2010 at 10:37 PM, Dave Filchak sub...@zuka.net wrote:
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,
If your secondaries can't reach the primary for the period of time you have
in your SOAs for refresh the secondaries wills top answering.
--
-Ben Croswell
On Thu, May 6, 2010 at 10:37 PM, Dave Filchak sub...@zuka.net wrote:
Our master server machine had a drive failure and looks like it will
On Thu, 2010-05-06 at 22:37 -0400, Dave Filchak wrote:
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
-users-bounces+bruce.ray=zionsbancorp@lists.isc.org
gt; lt;bind-users-bounces+bruce.ray=zionsbancorp@lists.isc.orggt;
gt; To: bind-users@lists.isc.org lt;bind-users@lists.isc.orggt;
gt; Sent: Thu May 06 21:37:35 2010
gt; Subject: Master server offline
gt;
gt; Our master server
: 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
Please fix your mail scanner. It is breaking the headers into two
parts by inserting a blank line (see below). This makes it very
hard to reply to you.
X-zuka-RWMailScanner-Watermark: 1273807139.93...@anxgbaayeoqp7eoxtwe51g
X-zuka-RWMailScanner-From: sub...@zuka.net
X-zuka-RWMailScanner-ID:
Dave, You are missing the X in the -zuka-rw-MailScanner: Found to be
clean line.
and it appears to not match the other X-zuka-RWMailScanner headers, this
may lead to problems, and no doubt if you --lint mailscanner it will
throw errors saying mismatch for SA.
On Fri, 2010-05-07 at 13:47 +1000,
13 matches
Mail list logo
