[Pdns-users] Disable slave seems impossible

[Aki Tuomi]

On Mon, Aug 24, 2015 at 07:32:00PM +0300, Aki Tuomi wrote:
> On Mon, Aug 24, 2015 at 02:46:59PM +0200, Giuseppe Ravasio wrote:
> > Hello,
> > I'm setting up two PowerDNS authoritative servers (Let's say ONE and
> > TWO) with MySQL backend and replication in Master-Master mode.
> > 
> > - 99% of domains will be in native mode
> > - some domains need to be in Master mode because they also have other NS
> > records or are hidden primary
> > - some domains need to be in Slave mode, because the customer is running
> > the master
> > 
> > Therefore I set on ONE:
> > master = yes
> > slave = no
> > 
> > And on TWO:
> > master = yes
> > slave = yes
> > only-notify=127.0.0.1
> > 
> > I set the only-notify because I do not need TWO to notify third party
> > DNS servers when acting as master.
> > 
> > It's all working fine except from the fact that also ONE tries to get
> > updated zones for the domains configured as SLAVE, even if I've put in
> > the config slave = no.
> > 
> > I'm missing something?
> > Setting "slave = no" isn't supposed to make pdns ignore all the records
> > with type set as SLAVE?
> > 
> 
> Setting slave=no disables slave *functionality*, it does not ignore domains.
> you probably should put them into a separate database, I'm pretty sure
> it will do what you expect this way.
> 

Looking at 3.4.5 sources, setting slave=no disables notification processing.
Unfortunately it seems not to disable slaveRefresh, which it should. This is
imo a bug.

Aki