No subject

C)
	(envelope-from news at google.com)
Received: from proxy.google.com ([216.239.35.5]:12095)
	by trinity.supernews.net with esmtp (Exim 4.20)
	id 19s2px-0006Fr-Jc
	for comp-protocols-dns-bind at moderators.isc.org; Wed, 27 Aug 2003 16:07:57
 +0000 Received: from sjmm36.sj.google.com (sjmm36.prod.google.com
 [10.6.39.36]) by proxy.google.com (8.12.8/8.12.8) with ESMTP id
 h7RG7SMD022740
	for <comp-protocols-dns-bind at moderators.isc.org>; Wed, 27 Aug 2003 09:07:28
 -0700 Received: (from news at localhost)
	by sjmm36.sj.google.com (8.12.9/8.12.9) id h7RG7SIh028696
	for comp-protocols-dns-bind at moderators.isc.org; Wed, 27 Aug 2003 09:07:28
 -0700 To: comp-protocols-dns-bind at isc.org
Path: not-for-mail
From: seals at dnsboss.com (Morris Seals)
Newsgroups: comp.protocols.dns.bind
Subject: Re: Mirroring DNS masters
Date: 27 Aug 2003 09:07:27 -0700
Organization: http://groups.google.com/
Lines: 52
Message-ID: <dc264c7f.0308270807.166f7125 at posting.google.com>
References: <bigblf$1tdf$1 at sf1.isc.org>
NNTP-Posting-Host: 64.58.17.61
Content-type: text/plain; charset=3DISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1062000448 28695 127.0.0.1 (27 Aug 2003 16:07:28
 GMT) X-Complaints-To: groups-abuse at google.com
NNTP-Posting-Date: 27 Aug 2003 16:07:28 GMT
Sender: bind-users-bounce at isc.org
Errors-to: bind-users-bounce at isc.org
Precedence: bulk
List-unsubscribe: <mailto:bind-users-request at isc.org?Subject=unsubscribe>
List-Id: <bind-users.isc.org>
X-List-ID: <bind-users.isc.org>

Dan,
     Yes this is an EXCELLENT idea!  The reason this is
such a great idea is that if you lose a server, you can
still do updates on the remaining server.  Also, you
don't have to worry about your primary and secondary
servers getting out of sync.  I would consider adding
one additional step to your configuration.  Check
the status code of the restart of named for errors before
you do your rdist.  This way you only push if there are
zero errors.  This is something that is automatically done
in a highly recommended 'Staging/Failover' configuration.
 If your site is large enough, you can add a hidden staging
server where updates are done to prevent your clients
from ever seeing bad DNS data.

=2DMorris Seals
 DNS Boss Inc.
 http://www.dnsboss.com
 720.339.1147

__________________________________________________________________

"Dan Brown" <dan at amanah.com> wrote in message
 news:<bigblf$1tdf$1 at sf1.isc.org>...

> Hi,
>
> I was just wondering if anyone mirrors their master domain name servers
> as either an exact mirror or a copied mirror for redundancy or load
> balancing.
> We have a couple of Cobalt RaQs which themselves are not hard to setup but
> rather than setting up master and slave nameservers, we would like to set=
up
> two master servers.  99% of DNS updates would occur on the one server and
> for the most part updating the zone files on the other server is going to
> be handled through a cron job and some scripting using SSH.
>
> By doing this we hope to acheive the complete redundancy of another master
> server (which would be listed as our secondary, but serves as a mirror on
> another network) rather than a secondary server whose records start to
> expire after 12 hours.
>
> I've done some searching on both the bind archives as well as Google but
> have only so far been getting hits referencing LDAP.  If anyone could poi=
nt
> me towards some documentation on either how to do configure mirrored DNS
> masters or what difficulties there are in attempting such a configuration,
> I greatly appreciate it.
>
>
> Dan Brown
> dan at amanah.com