[Pdns-users] Disable slave seems impossible
Peter van Dijk
peter.van.dijk at powerdns.com
Tue Aug 25 07:37:27 UTC 2015
On 25 Aug 2015, at 6:07, Aki Tuomi wrote:
> On Tue, Aug 25, 2015 at 06:44:54AM +0300, Aki Tuomi wrote:
>> 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:
>>>> It's all working fine except from the fact that also ONE tries to
>>>> updated zones for the domains configured as SLAVE, even if I've put
>>>> the config slave = no.
>>>> I'm missing something?
>>>> Setting "slave = no" isn't supposed to make pdns ignore all the
>>>> with type set as SLAVE?
>>> Setting slave=no disables slave *functionality*, it does not ignore
>>> you probably should put them into a separate database, I'm pretty
>>> it will do what you expect this way.
>> Looking at 3.4.5 sources, setting slave=no disables notification
>> Unfortunately it seems not to disable slaveRefresh, which it should.
>> This is
>> imo a bug.
I agree, this is a bug.
> If you are interested, you can try
> and commit there whether it works for you or not. This would help
I’m sorry to say we have decided not to merge this patch into 3.4.6.
We suspect there are many users accidentally relying on this behaviour,
and we do not want to risk breaking all their setups in a minor
As a workaround, assuming you are using gmysql, you could do something
gmysql-info-all-slaves-query=select id,name,master,last_check,type from
domains where 1=0
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/
More information about the Pdns-users