[Pdns-users] Problems with NAPTR records (Debian Sarge) [SOLVED]

[Kostas Zorbadelos]

On Thu, Mar 02, 2006 at 12:16:58PM +0200, Kostas Zorbadelos wrote:
> On Thu, Mar 02, 2006 at 10:24:05AM +0100, Norbert Sendetzky wrote:
> > Hi Kostas
> >
> Hello Norbert
>  
> > > dn: dc=3.1.2.8.9.8.3.0.1.2.0.3,dc=e164.arpa,ou=domains,dc=otenet,dc=gr
> > > changetype: add
> > > objectclass: otenetDNSDomain
> > > objectclass: domainrelatedobject
> > > dc: 3.1.2.8.9.8.3.0.1.2.0.3
> > > associateddomain: 3.1.2.8.9.8.3.0.1.2.0.3.e164.arpa
> > > NAPTRRecord: 10 100 u E2U+sip !^.*$!sip:prod2 at 212.205.221.1!
> > >
> > > Is something wrong to the way NAPTR records are stored in ldap?
> > 

Sometimes the solutions to problems lie just in front of our eyes.
I had used the zone2ldap script to convert the BIND zone to LDAP
entries for use by PowerDNS. That script produced the output for NAPTR
records like

NAPTRRecord: 10 100 u E2U+sip !^.*$!sip:prod2 at 212.205.221.1!

while the correct value should be

nAPTRRecord=10 100 "u" "E2U+sip" "!^.*$!sip:kmar at sip1.sip.otenet.gr!".

exactly what it was in the BIND zone conf file.

Now PowerDNS answers questions for NAPTR just fine.

Thanks for everything 
Kostas

PS: The problem with linux ldapsearch against the SUN JES directory
(it shows the NAPTR value as binary) still remains.


-- 
  Kostas Zorbadelos
  m at il contact: kzorba (at) otenet.gr
  
  Out there in the darkness, out there in the night
  out there in the starlight, one soul burns brighter
  than a thousand suns.