two masters for the same zone

[Brad Knowles]

At 5:31 PM -0400 2005-08-07, srg wrote:

>  I need the following scenario:
>
>  1. two or more nameservers (ns1, ns2, ...) MASTERS of the same zone, ie,
>  example.com.

	Why do they both have to be masters?  Why can't one be a master 
and the other a slave?

>  2. one or more clients do ddns updates to the nameservers in (1). Those
>  updates will be done sometimes to ns1 and other times to ns2.

	Again, why?

>  Here comes de problem:
>  3. If a client registers it's name (client1) in ns1's example.com. zone
>  then I need that the name client1.example.com. to be resolved in ns1 AND
>  IN ns2.

	This problem is resolved for you automatically, if ns1 is the 
master and ns2 is the slave.  Both are fully authoritative, of course.

>  4. The same if the client registers in ns2's example.com. zone (the name
>  MUST be resolved in ns1 and in ns2).

	Again, this is resolved for you automatically if you don't make 
them both masters.

>  I have been done a similar configuration but configuring ns2 as a SLAVE
>  (including to do the updates in the slave and then the salve forward the
>  update request to the master), but the problem is that if ns1 goes down
>  then no more clients can be registered.

	So make sure that ns1 doesn't go down, or that you get notified 
of this problem immediately.  The alternative you've come up with is 
much nastier and more complex to solve.

-- 
Brad Knowles, <brad at stop.mail-abuse.org>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

     -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
     Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See <http://www.sage.org/> for more info.