I understand you,
but the advantage of having mysql backend is that if one of the two servers dies, the other keeps running with up to date informations, and can also be updated wit new informations. When the other server comes up again it will automatically sync itself using mysql replica mechanism. if I use file backend I have to manually sync
it, and how to keep tracks of modifications ?

for this I choose mysql backend

Riccardo


On 2/11/11 10:29 PM, David Sparro wrote:
On 2/9/2011 7:12 PM, fddi wrote:


I could succesfully setup bind with mysql backend and it works using
bind-mysql driver.

everything works except that nsupdate will no longer work.

is this normal ??

requests sent for adding a RR using nsupdate are ignored by named when
using mysqldb backend
while they are honoured and served when using normal file backend.

is this a normal behaviour ?

how to use nsupdate even if with a different backend which is not the
default file backend ?



If you are using nsupdate to make changes to your hosted zones, couldn't you simply change the process to send the update to both servers separately. Make each server a master with a standard file for the backend data.


_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to