[Pdns-users] Pdns answer for non-existing zones
gaetan at nexylan.com
Thu Feb 23 15:40:05 UTC 2012
Right, but technically, a serverfail reply makes the end-user (browser,
os) rely on other DNS servers for resolving the zone. Whereas the reply
provided by 3.0.1 does not.
This night, after the upgrade, we had thousands of websites that went down
(50% time when query got on pdns without zone) because of this change.
Emergency solution has been to shut powerdns down and make websites rely
on primary dns only, they went back online immediately.
Le 23/02/12 16:33, « Peter van Dijk » <peter.van.dijk at netherlabs.nl> a
>On Feb 23, 2012, at 16:18 , Gaëtan Allart wrote:
>> And this IS the issue. When it does not have the zone loaded (in version
>> 3.0.1) it does not respond with serverfail whereas previous versions did
>> I've just downgraded to 18.104.22.168 and it works fine now. When zone is not
>> loaded, pdns return serverfail to end-users who, then, rely on other NS
>> the zones.
>> This behavior does not work with 3.0.1 (same config file).
>Both 22.214.171.124 and 3.0.1 are reporting, in their own way, that they do not
>have the zone. There is no strong consensus on what the right answer is
>(some name servers even decide to not respond at all).
>A recursor should be fine with both behaviours; and you should not be
>creating a setup that even relies on recursor falling back from one
>machine to the other. If you could explain -why- you want this, perhaps
>we can propose a different solution.
>Peter van Dijk
>Pdns-users mailing list
>Pdns-users at mailman.powerdns.com
More information about the Pdns-users