I can't replicate with 3.0.1 so I don't think its in any current code. Barring a regression of course. Idk what he is running but it is possible that its old and affected. Can't be sure since I can't investigate directly. On Dec 15, 2013 11:40 PM, "Peter van Dijk" <peter.van.d...@netherlabs.nl> wrote:
> Hello folks, > > I have not followed this thread (I saw it was full of helpful people > already!), but I would just like to point out that that bug is actually 8 > years old -- our github migration could not copy the timestamps reliably. > The fix was in version 2.9.20, released March 2006. > > That said, if anybody does think a bug has been found in a recent > PowerDNS, we're happy to look into it! > > Kind regards, > -- > Peter van Dijk > Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ > > On Dec 13, 2013, at 23:54 , Michael Loftis wrote: > > > Ah...You actually *may* have hit a bug. What version of powerdns and > > what backend? There's an issue on github, number 49, fixed in commit > > number 549 according to the bug where PDNS was behaving similar to > > this...if you dig for things *under* that subdomain eg > > test.labisilon.lab.domain.com you get the correct response (NS and A > > records w/ no AA bit indicating you must chase the delegation) -- but > > when querying for the delegated domain, it returns the SOA and an AA > > bit w/ NXDOMAIN indicating no such record. > > https://github.com/PowerDNS/pdns/issues/49 > > > > _______________________________________________ > Pdns-users mailing list > Pdns-users@mailman.powerdns.com > http://mailman.powerdns.com/mailman/listinfo/pdns-users > >
_______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
