Jeff Waugh wrote:
<quote who="Philip Greggs">

OP was using dc=example,dc=com and RFC 3663 says in this case the domain
is example.com.

Dude, you can use gobbledegook in a DN.

This is not true that you can use gobbledegook in a DN. That's the
reason for the SCHEMAS and RFCs, to keep DN etc in line with standards. There
are two standards X.500 and IETF. You use anything else then you don't
obey the standards at the perils of having errors in your LDAP
implementations.
It doesn't have to have anything to
do with a DNS name. They're unrelated until the point that you decide to
relate them by inference. There is nothing special about their relationship
in the LDAP protocol.

Clearly the original poster is using IETF standard. If he were using
X.500 standard he would have

Portion of his slapd.conf would be,
suffix "o=Example Company,c=AU'
rootdn "cn=Manager,o=Example Company,c=AU"

His top DN in ldif would be,
dn: o=Example Company,c=AU
objectClass: organization
o: Example Company

But clearly he is using IETF because he has
1. slapd.conf
....
suffix "dc=example,dc=com"
rootdn "cn=Manager,dc=example,dc=com"

2.His top DN
dn: dc=example,dc=com
dc: example
etc

In view of LDAP standard in RFC 3663 as stated
by one poster previous the original poster's domain name is
example.com

Hope this helps.

O Plameras












An LDAP client has to figure out which LDAP server and DN it wants to use,
through configuration or direct user manipulation of the tool. They could be
utterly different, or interestingly similar, but you can't guarantee that
one could be derived from the other, in either direction. :)

- Jeff


--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to