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 received a lot of fixes in 2.9.21, so perhaps >> you >> could try that. > > We've been using NAPTR records in PowerDNS long before 2.9.21, although > somewhere between 2.9.16 (I think) and later versions there was a bug > introduced because I tried to upgrade and ended up down grading as a > result. > > As for the original questions of correct structuring. > > # dig 5.5.3.8.5.5.5.0.0.8.1.e164.org NAPTR +short > 200 10 "u" "E2U+SIP" > "!^\\+1800(.*)$!sip:[EMAIL PROTECTED]" . > 200 10 "u" "E2U+SIP" "!^\\+1800(.*)$!sip:[EMAIL PROTECTED]" . > > -- > > Best regards, > Duane > > http://www.freeauth.org - Enterprise Two Factor Authentication > http://www.nodedb.com - Think globally, network locally > http://www.sydneywireless.com - Telecommunications Freedom > http://e164.org - Because e164.arpa is a tax on VoIP > > "In the long run the pessimist may be proved right, > but the optimist has a better time on the trip." > _______________________________________________ > Pdns-users mailing list > [email protected] > http://mailman.powerdns.com/mailman/listinfo/pdns-users > > -- View this message in context: http://www.nabble.com/problem-with-naptr-answer-tf4917905.html#a14149417 Sent from the PowerDNS mailing list archive at Nabble.com. _______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
