Uprading pdns to 2.9.21-3 did the job - it's working fine now :-)
Thanx a lot!
evilbunny wrote:
>
> bert hubert wrote:
>> On Fri, Nov 30, 2007 at 07:56:18AM -0800, Eli.Birova wrote:
>>> I am using 2.9.20 on Debian with gpgsql backend. We are trying to set up
>>
>> Quick answer is that NAPTR r
bert hubert wrote:
> On Fri, Nov 30, 2007 at 07:56:18AM -0800, Eli.Birova wrote:
>> I am using 2.9.20 on Debian with gpgsql backend. We are trying to set up
>
> Quick answer is that NAPTR received a lot of fixes in 2.9.21, so perhaps you
> could try that.
We've been using NAPTR records in PowerDN
On Fri, Nov 30, 2007 at 07:56:18AM -0800, Eli.Birova wrote:
> I am using 2.9.20 on Debian with gpgsql backend. We are trying to set up
Quick answer is that NAPTR received a lot of fixes in 2.9.21, so perhaps you
could try that.
Good luck!
--
http://www.PowerDNS.com Open source, database dr
Hi All,
I am using 2.9.20 on Debian with gpgsql backend. We are trying to set up
pdns to be used for enum lookup from an SBC.
The problem is that the SBC is expecting to receive the NAPTR answer in the
following form:
100 10 "u" "E2U+sip" "!^.*$!sip:[EMAIL PROTECTED]"
and the answer comes as fol
