[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
I'm getting different results returned from two identical LDAP servers, one running 2.0 and the other 2.1...
- To: <openldap-software@OpenLDAP.org>
- Subject: I'm getting different results returned from two identical LDAP servers, one running 2.0 and the other 2.1...
- From: "Kyle Stone" <KStone@corp.halfpricehosting.com>
- Date: Thu, 20 Mar 2003 15:56:06 -0500
- Content-class: urn:content-classes:message
- Thread-index: AcLvIyBSAPEz2r5WT2m0bY+FZ6wc5g==
- Thread-topic: I'm getting different results returned from two identical LDAP servers, one running 2.0 and the other 2.1...
I've looked for several hours and can't find any documentation
reguarding major differences in these two.
How ever, here's the scenario:
My directory is layed out as such..
dn: o=base
"dn: cn=domain1.com, o=base" It has an
objectclass: dnszone
"dn: cn=A,cn=domain1.com" It has an
objectclass: dnsrrset and is a child record of "dn: cn=domain1.com,
o=base"
"dn: cn=domain2.com, o=base"
"dn: cn=A,cn=domain2.com"
"dn: cn=domain3.com, o=base"
"dn: cn=A,cn=domain3.com"
And etc with lots and lots of records and sub-records..
Anyways.. I do this...
"ldapsearch -b o=base -D"cn=manager,o=base" -W '(objectclass=DNSzone)'
dn -h ldapv2.host.com"
and I get this..
version: 2
#
# filter: (objectclass=DNSzone)
# requesting: dn
#
# domain1.com base
dn: cn=domain1.com, o=base
# domain2.com base
dn: cn=domain2.com, o=base
# domain3.com base
dn: cn=domain3.com, o=base
Now if I search against the v3 host, I get..
"ldapsearch -b o=base -D"cn=manager,o=base" -W '(objectclass=DNSzone)'
dn -h ldapv3.host.com"
# extended LDIF
#
# LDAPv3
# base <o=dns> with scope sub
# filter: (objectclass=DNSzone)
# requesting: dn
#
# domain1.com base
dn: cn=domain1.com, o=base
# A:, domain1.com base
dn: cn=A:, cn=domain.com, o=base
# domain2.com base
dn: cn=domain2.com, o=base
# A:, domain2.com base
dn: cn=A:, cn=domain2.com, o=base
# domain3.com base
dn: cn=domain3.com, o=base
# A:, domain3.com base
dn: cn=A:, cn=domain3.com, o=base
Why am I seeing the children records of a matching object class when the
children don't match the objectclass I'm filtering on?
Has default scoping changed from OpenLDAP 2.1.12 and OpenLDAP
2.0.25-Release?
I can get the exact same results from the V3 as the V2 server, if I
change the scoping to one-level on the V3 server.
I checked the slapd.conf and the indexes for the objectclass is the same
on both.
Kyle Stone
kstone@corp.halfpricehosting.com