bert hubert wrote:
> Just so you know, the freeware you are relying on is pretty close to malware..
>
Wow, that's not even funny. Honestly, this kind of FUD should be illegal.
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailma
Samuel Vogel wrote:
setup powerdns on the server which contains all our customer data and
configure it as a supermaster. But it should not answer incoming dns
requests itself, but just keep our real dns servers (now running
powerdns) up to date. I would use a file based backends to eliminate
t
the results, and there is a bug in my other client software that was
causing queries not to match for an entirely unrelated reason, for which
I'll submit a bug with the responsible developers.
Again, apologies for wasting everyone's time.
Rega
Just a test message.
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
Peter Fern wrote:
Hi Bert,
bert hubert wrote:
Can you try doubling the \, so:
100 0 "u" "E2U+sip" "!^\\+([0-9][0-9][0-9])$!sip:[EMAIL PROTECTED]" .
As I thought - the slashes are returned verbatim when doubled, and
cause the parser to barf when there is onl
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
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 returni
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&#x
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
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
etely - any pointers in the right direction would be a great help.
Peter Fern wrote:
Hi Bert,
bert hubert wrote:
Can you try doubling the \, so:
100 0 "u" "E2U+sip" "!^\\+([0-9][0-9][0-9])$!sip:[EMAIL PROTECTED]" .
As I thought - the slashes are returned verbatim
Hi Bert,
bert hubert wrote:
Can you try doubling the \, so:
100 0 "u" "E2U+sip" "!^\\+([0-9][0-9][0-9])$!sip:[EMAIL PROTECTED]" .
As I thought - the slashes are returned verbatim when doubled, and cause
the parser to barf when there is only one:
Here is the result with a single '\':
mysq
bert hubert wrote:
On Tue, Jul 29, 2008 at 05:08:26PM +1000, Peter Fern wrote:
No one else is serving NAPTR E2U expressions from PowerDNS?
Peter,
Sorry for the late replay. In fact, quite a number of people are doing such
things with PowerDNS.
No problem Bert, thank you for the
No one else is serving NAPTR E2U expressions from PowerDNS?
Peter Fern wrote:
Hello list,
I am attempting to serve NAPTR records with E2U regular expressions,
requiring escaping of characters by employing a '\', eg:
100 0 "u" "E2U+sip" "!^\+([0-9][0-9][0
sequences when parsing a record? And more to the point, is there an
easy way to fix this behaviour.
Regards,
Peter Fern
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
15 matches
Mail list logo
