Bug#438480: [EMAIL PROTECTED]: Bug#438480: pdns_recursor leaks all over the place]

2007-08-21 Thread bert hubert
On Tue, Aug 21, 2007 at 03:28:05PM +0200, martin f krafft wrote: > I can confirm that a value of 10 (a hundred thousand) > approximately halved the RAM consumption of the recursor. It would > be able to impose a hard limit in terms of bytes, not number of > records. That would indeed be suprem

Bug#398213: issue most probably fixed

2007-03-25 Thread bert hubert
This issue has most probably been addressed by the move to a whole new zone parser, plus http://wiki.powerdns.com/cgi-bin/trac.fcgi/changeset/984 Please verify using SVN HEAD of PowerDNS. -- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl

Bug#406465: Info received (Bug#406465: Info received (more details needed please (zone data)))

2007-03-01 Thread bert hubert
Your fix looks perfect for the interim, many thanks! On Thu, Mar 01, 2007 at 10:42:56AM +0100, Andreas Henriksson wrote: > On Thu, Mar 01, 2007 at 12:29:48AM +0100, bert hubert wrote: > > I fail to reproduce the bug. PowerDNS does misparse the ( record, which is > > sad, and fi

Bug#406465: Info received (more details needed please (zone data))

2007-02-28 Thread bert hubert
I am working on a fix now, and hope to release it within an hour. Bert On Fri, Feb 16, 2007 at 08:18:03PM +, Debian Bug Tracking System wrote: > Thank you for the additional information you have supplied regarding > this problem report. It has been forwarded to the package maintainer

Bug#406465: Info received (Bug#406465: Info received (more details needed please (zone data)))

2007-02-28 Thread bert hubert
I fail to reproduce the bug. PowerDNS does misparse the ( record, which is sad, and fixed in SVN (the fix is intrusive and should not be backported probably). But although we misparse the record, I don't see the other behaviour your mention. Can you give me a step-by-step so I can see your proble

Bug#406465: more details needed please (zone data)

2007-02-16 Thread bert hubert
Jeroen (and Bas I assume), Can you provide me with a copy of your problematic a-eskwadraat zone? Thanks -- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] w

Bug#398213: this bug is related to broken zone parser

2006-11-12 Thread bert hubert
This bug is not general and exists only in zones that end on a TXT record with braces "(" in them. The bug has been entered in the powerdns bug tracker. -- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services -

Bug#382538: Info received (geobackend bug)

2006-08-13 Thread bert hubert
Mark Bergsma and I successfully debugged this issue, which may previously have been hidden by a g++ misfeature/bug. Mark's fix is in http://wiki.powerdns.com/projects/trac/changeset/876 - which also addresses some other geobackend issues. Thanks for the bug report, and thanks to Mark for the quick

Bug#382538: geobackend bug

2006-08-13 Thread bert hubert
Peter, Can you send me all your configuration files? I'll take a look at it. In the meantime, you might try reproducing this bug with upstream powerdns if possible. Thanks. -- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Clo

Bug#327846: fixed in svn but hard to backport to 2.9.18

2005-09-25 Thread bert hubert
Laurent, Matthijs, The problem you report is no longer in 2.9.19 as it has a different bindbackend. However, this does not help debian as 2.9.19 is rather a break with 2.9.18, replacing the entire bindbackend with a new implementation, possibly with new bugs. Given the amount of time I have avai

Bug#320638: any clue on when this will be fixed? or workaround?

2005-07-31 Thread bert hubert
Thanks for the clarification - any idea on when this will be fixed? Is there a workaround? Thanks. -- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a