[Pdns-users] Problems with NAPTR records (Debian Sarge)
Kostas Zorbadelos
kzorba at otenet.gr
Thu Mar 2 09:21:46 UTC 2006
On Thu, Mar 02, 2006 at 07:53:35PM +1100, Duane wrote:
> Kostas Zorbadelos wrote:
>
> >The backend for the zones you are authoritative is still MySQL or
> >something else?
> >Anyway, unfortunately LDAP is a hard requirement for us, so unless I
> >hear something that will make it work with pdns, I will have to look
> >for alternatives.
>
> My point is, I don't see why it wouldn't work, I know it works perfectly
> well with the MySQL backend...
>
In my previous post I described that while queries for other record
types are answered, queries for NAPTR records fail.
For example I have the following entries in LDAP:
dn: dc=e164.arpa,ou=domains,dc=otenet,dc=gr
changetype: add
objectclass: otenetDNSDomain
objectclass: domainrelatedobject
dc: e164.arpa
associateddomain: e164.arpa
SOARecord: tagoba.otenet.gr root 2006022801 10800 36288000 604800 86400
dn: dc=e164.arpa,ou=domains,dc=otenet,dc=gr
changetype: modify
add: NSRecord
NSRecord: tagoba.otenet.gr
dn: dc=6.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: 6.1.2.8.9.8.3.0.1.2.0.3
associateddomain: 6.1.2.8.9.8.3.0.1.2.0.3.e164.arpa
NAPTRRecord: 10 100 u E2U+sip !^.*$!sip:kmar at sip1.sip.otenet.gr!
Now if I do
kzorba at tagoba(0)[11:08 AM]~>dig -t SOA e164.arpa @tagoba
; <<>> DiG 9.2.4 <<>> -t SOA e164.arpa @tagoba
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10198
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;e164.arpa. IN SOA
;; ANSWER SECTION:
e164.arpa. 3600 IN SOA tagoba.otenet.gr. root. 2006022801 10800 36288000 604800 86400
;; Query time: 5 msec
;; SERVER: 62.103.146.237#53(tagoba)
;; WHEN: Thu Mar 2 11:10:53 2006
;; MSG SIZE rcvd: 83
Logs from pdns:
Mar 2 11:10:53 tagoba pdns[24090]: Query: 'e164.arpa|ANY'
Mar 2 11:10:53 tagoba pdns[24090]: Query: 'e164.arpa|SOA'
kzorba at tagoba(0)[11:10 AM]~>dig -t NS e164.arpa @tagoba
; <<>> DiG 9.2.4 <<>> -t NS e164.arpa @tagoba
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30149
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;e164.arpa. IN NS
;; ANSWER SECTION:
e164.arpa. 3600 IN NS tagoba.otenet.gr.
;; Query time: 7 msec
;; SERVER: 62.103.146.237#53(tagoba)
;; WHEN: Thu Mar 2 11:12:20 2006
;; MSG SIZE rcvd: 57
All these are OK.
BUT if I do:
kzorba at tagoba(0)[11:13 AM]~>dig -t NAPTR 6.1.2.8.9.8.3.0.1.2.0.3.e164.arpa @tagoba
; <<>> DiG 9.2.4 <<>> -t NAPTR 6.1.2.8.9.8.3.0.1.2.0.3.e164.arpa @tagoba
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29985
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;6.1.2.8.9.8.3.0.1.2.0.3.e164.arpa. IN NAPTR
;; Query time: 3 msec
;; SERVER: 62.103.146.237#53(tagoba)
;; WHEN: Thu Mar 2 11:14:06 2006
;; MSG SIZE rcvd: 51
pdns logs:
Mar 2 11:14:06 tagoba pdns[24090]: Query: '6.1.2.8.9.8.3.0.1.2.0.3.e164.arpa|ANY'
LDAP logs:
02/Mar/2006:11:15:42 +0200] conn=49 op=3 msgId=4 - SRCH base="ou=domains,dc=otenet,dc=gr" scope=2 filter="(associatedDomain=6.1.2.8.9.8.3.0.1.2.0.3.e164.arpa)" attrs="dNSTTL aRecord nSRecord cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord rprecord aAAARecord LocRecord sRVRecord nAPTRRecord"
[02/Mar/2006:11:15:42 +0200] conn=49 op=3 msgId=4 - RESULT err=0 tag=101 nentries=1 etime=0
As I can see, the ldap query is issued, LDAP server responds with the
NAPTR record but this is not included in the DNS answer!
I am afraid that perhaps the entry for NAPTR record is stored wrongly
in LDAP, or is corrupted somehow.
If anyone has accomplished the setup I describe, I would love to hear
about it.
Thanks,
Kostas
--
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.
More information about the Pdns-users
mailing list