[Pdns-users] Pdns 2.9.22 stopped treating NOTIFY or manual retrieves when acting as slave

Florent Lerat flow at k-ribou.com
Mon Oct 4 12:09:16 UTC 2010

Le 4 oct. 2010 à 12:24, bert hubert a écrit :

> On Mon, Oct 04, 2010 at 12:06:22PM +0200, Florent Lerat wrote:
>> Hi there,
>> We have been using PowerDNS for a few years without a problem. However,
>> since a few days, we are dealing with an issue I can't resolve.
>> We are using 5 servers running the same PowerDNS version. 3 of those 5
>> recently stopped updating when receiving a valid notify from a master
>> server.
> How many domains do you slave? From how many different masters?
> Can you check if perhaps some of those masters are generating timeouts?
> 	Bert

We slave about 200000 domains for most of which one of our 5 servers is the master.

We are slave for 90 different masters. Some of those masters are indeed generating timeout or different types of error such as :
- Query to '' for SOA of 'domain' produced a NS record
- Remote nameserver reported error: RCODE=5
- Remote nameserver reported error: RCODE=2

They are caused by incorrectly configured masters (AXFR not allowed) or because the domain name does not exist anymore but is still in our slave database.

Most of our domains are correctly configured thought.

We use 5 different servers, with different loads :
- Server1 : pdns 2.9.22
- Server2 : pdns 2.9.22
- Server3 : pdns 2.9.22
- Server4 : pdns
- Server5 : pdns

Server 1,2 & 3 are affected by the issue, they are also the ones with the heavier load. Server4 & Server5 does not seems to be affected by the issue.



More information about the Pdns-users mailing list