On 05/08/10 17:36, Chris Thompson as IP Register wrote:
On May 7 2010, Peter Laws wrote:
If he has a small number of slaves, the OP may not need a Tardis. It's
If you do this, you need to restart BIND on the slave to have it notice
the change. Similarly you can "touch" the zone file to mak
In article ,
Bruce Ray 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 things on a Friday, have a
week off and then fix them again on the Monday morni
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
In article ,
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
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
poss
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 t
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
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: A0
In article ,
Dave Filchak wrote:
> 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?
The glue records don't distinguish between masters and slaves.
But it would be
Secondaries need to 'know' that this old sec is now a master as well.
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.
--
-___
David Miller
Ti
In article ,
Bruce Ray 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 com
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
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 wrote:
> Our master server machine had a drive failure and looks like it will be
> offline f
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 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
>
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.
From: bind-users-bounces+bruce.ray=zionsbancorp@lists.isc.org
To: bind-users@lists.isc.org
Sent: Thu May 06 21:37:35 2010
15 matches
Mail list logo
