Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Peter Fern wrote: > What version are you running? The problem that sparked this thread is > that <2.9.21 bind backend doesn't handle NAPTR, and =2.9.21 includes the > MOADNSParser, which doesn't handle backslashes correctly for at least > gmysql (I assume for every backend). We've used from 2.9.

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Duane wrote: I've never had a problem with \+ in PDNS... What version are you running? The problem that sparked this thread is that <2.9.21 bind backend doesn't handle NAPTR, and =2.9.21 includes the MOADNSParser, which doesn't handle backslashes correctly for at least gmysql (I assume f

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Peter Fern wrote: > Correct, however we often have a requirement to match a substring and > sub it into another pattern to translate one number range to another, > hence the requirement for regex. And regardless - it's currently > impossible to escape characters like '+' since the backslashes are

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Duane wrote: Peter Fern wrote: All I'm trying to do is get PDNS to return a record verbatim from the backend (actually, I've just reviewed the RFC, which says a double-backslash in the zone must return a single in the response). Simply matching '\\' and returning '\' is a low-cost operation

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Peter Fern wrote: > All I'm trying to do is get PDNS to return a record verbatim from the > backend (actually, I've just reviewed the RFC, which says a > double-backslash in the zone must return a single in the response). > Simply matching '\\' and returning '\' is a low-cost operation, and > req

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Duane wrote: Peter Fern wrote: Duane wrote: It's pointless trying to expand regular expressions from within the DNS server, either it will increase load unnecessarily or the regular expressions were designed to be expanded by a client requesting the information. I'm aware tha

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Peter Fern wrote: > Duane wrote: >> It's pointless trying to expand regular expressions from within the DNS >> server, either it will increase load unnecessarily or the regular >> expressions were designed to be expanded by a client requesting the >> information. >> > > I'm aware that parsing o

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Duane wrote: It's pointless trying to expand regular expressions from within the DNS server, either it will increase load unnecessarily or the regular expressions were designed to be expanded by a client requesting the information. I'm aware that parsing of the regex is meant to be done clie

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Peter Fern wrote: > Duane wrote: >> Peter Fern wrote: >> >>> Can anyone point me to roughly where I should be looking in the codebase >>> to patch this out? I imagine somewhere in this new universal parser? I >>> assume it will only be a couple of lines to fix, but I don't have the >>> spare he

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Duane wrote: Peter Fern wrote: Can anyone point me to roughly where I should be looking in the codebase to patch this out? I imagine somewhere in this new universal parser? I assume it will only be a couple of lines to fix, but I don't have the spare headspace right now to come to grips wit

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Peter Fern wrote: > Can anyone point me to roughly where I should be looking in the codebase > to patch this out? I imagine somewhere in this new universal parser? I > assume it will only be a couple of lines to fix, but I don't have the > spare headspace right now to come to grips with another c

[Pdns-users] pdns-recursor performance

A big congrats on the performance of the pdns-recursor. We recently switched from bind8 to bind9 (because of the recent dns vulnerabilities) then to pdns-recursor (because of performance and stability issues). After the upgrade to pdns-recursor cpu utilisation dropped to 10% from 50% with bi

Re: [Pdns-users] Exception: unknown escape sequence on NAPTR regex

Can anyone point me to roughly where I should be looking in the codebase to patch this out? I imagine somewhere in this new universal parser? I assume it will only be a couple of lines to fix, but I don't have the spare headspace right now to come to grips with another codebase completely - a

Re: [Pdns-users] powerdns segfaulting?

On Mon, Aug 04, 2008 at 12:43:23PM -0700, Daniel Greene - (mt) Media Temple wrote: > Bert, > > Is there any word on the status of this possible race condition? > > Additionally, would checking the internal web interface tickle the same > code that could trigger this condition? Perhaps - what yo

Re: [Pdns-users] powerdns segfaulting?

Bert, Is there any word on the status of this possible race condition? Additionally, would checking the internal web interface tickle the same code that could trigger this condition? Best, -- Daniel Greene Systems Engineer (mt) Media Temple, Inc 877 578.4000 x515 - Original Message -