I understand you cannot support this request. But, for sure, NOERROR does not cause recursors to try the other nameservers. The thousands of websites that went down this night can prove it.
I know my setup is not perfect but this is the best we can. Our customers are free to use our powerdns for secondary dns service, even if they "forgot" to transmit us the configuration. Gaëtan Le 23/02/12 16:41, « Peter van Dijk » <[email protected]> a écrit : >Hi, > >On Feb 23, 2012, at 16:40 , Gaëtan Allart wrote: > >> Hello Peter, >> >> 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. > >Again, both the 2.9.22.5 and 3.0.1 responses should cause recursors to >try the other nameserver; additionally, SERVFAIL caused other problems, >which is why we moved to NOERROR. > >What you are reporting is not a bug and we cannot support your situation. >You are likely to have bundles of hidden breakage in your setup, even >with the 2.9.22.5 behaviour. > >Kind regards, >Peter van Dijk >_______________________________________________ >Pdns-users mailing list >[email protected] >http://mailman.powerdns.com/mailman/listinfo/pdns-users _______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
