Hi Rémi,
> I have been testing with 2.9.22.6, but I get the same results with Powerdns
> 3.0.
This should be fixed with SVN revision 2510. Thanks for the report!
Kind regards,
Peter van Dijk
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
Hi Peter,
Thank you for your response.
I believe both responses are valid; but I'm not seeing the behaviour you
describe. When I test with PowerDNS 3.0 the NS-records always end up in
AUTHORITY - what version are you running?
I have been testing with 2.9.22.6, but I get the same results wit
Hello Rémi,
On Mar 16, 2012, at 14:45 , Peter van Dijk wrote:
> Hello Rémi,
>
>
> On Mar 16, 2012, at 14:31 , Remi Gacogne wrote:
>
>> I noticed a difference in the behavior of bind, powerdns (using bind or
>> MySQL backend) and nsd regarding the answer to an NS query
>> for a delegated zone.
On Fri, Mar 16, 2012 at 02:31:34PM +0100, Remi Gacogne wrote:
>
> Hi,
>
> I noticed a difference in the behavior of bind, powerdns (using bind
> or MySQL backend) and nsd regarding the answer to an NS query
> for a delegated zone. Powerdns is responding to the query by putting
> corresponding NS
Hello Rémi,
On Mar 16, 2012, at 14:31 , Remi Gacogne wrote:
> I noticed a difference in the behavior of bind, powerdns (using bind or MySQL
> backend) and nsd regarding the answer to an NS query
> for a delegated zone. Powerdns is responding to the query by putting
> corresponding NS RRs into
Hi,
I noticed a difference in the behavior of bind, powerdns (using bind or
MySQL backend) and nsd regarding the answer to an NS query
for a delegated zone. Powerdns is responding to the query by putting
corresponding NS RRs into the ANSWER section,
whereas bind and nsd are putting them into
