[Pdns-users] adding non-native replication to existing shared backend

Jeffrey Wong mindstormmaster+pdns at gmail.com
Tue Nov 20 19:09:04 UTC 2007


I have two pdns servers that share a common mysql backend.  I want to
add a third pdns server with its own backend.  This new server is
located elsewhere and using native replication isn't feasible because
of the volume of data that would be sent by mysql (the database server
has many other databases on it).  When I enable master on one of the
two servers, I get a ton of messages in the logfile:

Nov 20 10:41:43 pink pdns[9504]: Queued notification of domain
'<domain>' to <2nd ip>
Nov 20 10:41:43 pink pdns[9504]: Queued notification of domain
'<domain>' to <local ip>
Nov 20 10:41:43 pink pdns[9504]: Received NOTIFY for <domain> from
<local ip> but slave support is disabled in the configuration
Nov 20 10:41:44 pink pdns[9504]: Received unsuccesful notification
report for '<domain>' from <local ip>, rcode: 4
Nov 20 10:41:44 pink pdns[9504]: Removed from notification list:
'<domain>' to <local ip>

where domain is any one of the domains managed by pdns, local ip is
the ip of the server set to master, and 2nd ip is the ip of the 2nd
pdns server.

Is there a way to not send notifications to yourself and only send to
the servers that ask for notifications?  Or is there a way to get rid
of these messages?

Thanks.


More information about the Pdns-users mailing list