[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ispman-users
Subject:    [Ispman-users] Pri/Sec DNS
From:       Ingar_Øyahals <yatzy () totem ! fix ! no>
Date:       2004-04-30 12:18:15
Message-ID: 20040430135434.V77608 () totem ! fix ! no
[Download RAW message or body]

Hello users @ ispman,

Am I correct when assuming that Ispman by design adds *master* entries in
both primary and secondary name server for new domains created via the web
gui? (Tested with both Bind9 && Bind9-sdbldap backend).

If so, I'd *really* like to know if anyone have workarounds that makes
secondary name server act as a slave server for domains created.
(Still talking Bind9 backend for dns management).

Running multiple master name servers for domains aren't very satisfactory
imho. If you change/add records for domain.com, and for some reason (hey,
errors happen all the time) only one of the name servers are updated with new
zoneinfo, the nameservers are out of sync, and we have two master name
servers spreading unequal information for domain.com!
(Again, if my assumptions are correct).

Really, I can't see the reason why ispman should let secondary name server
act as slave by default, but this is more a developer related question I
guess. Does anyone else have arguments for this design I'd appreciate
some feedback.

Thanks in advance for Your replies.

--
Sincerely,
Ingar Oyahals
yatzy@totem.fix.no


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Ispman-users mailing list
Ispman-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ispman-users
[prev in list] [next in list] [prev in thread] [next in thread]