Gonzalo Servat wrote:
On 4/20/06, O Plameras <[EMAIL PROTECTED]> wrote:
So, how will you explain the fact that the setup which I have just
illustrated
generates exactly the same error as the OP ?
I can't explain something that you've done. What I *can* show you, to
prove my point (and Jamies', while we're at it) is that the base dn
has no relation to DNS whatsoever. See for yourself:
(relevant parts from slapd.conf):
suffix "dc=slug,dc=org,dc=au"
rootdn "cn=Manager,dc=slug,dc=org,dc=au"
# ldapsearch -x -W -D 'cn=Manager,dc=slug,dc=org,dc=au'
Enter LDAP Password:
# extended LDIF
#
# LDAPv3
<etc ...>
To further prove my point, a tcpdump on port 53 revealed no activity
when doing an ldapsearch or restarting LDAP, so I'm not sure at which
point you seem to think some part of LDAP executes a DNS query to
check the existance of the domain defined as the base DN.
When you do an 'LDAP QUERY' DNS is queried will be or will not be
depending on how
you configure your LDAP client. In the case of the original thread I am
assuming the LDAP
Server is coded as hostname in the Client.
1. Regardless as to how the client is configured it has to find the LDAP
Server. There are two ways to do this,
a. If the IP Address is hardcoded at the client side, and in this
case there is no DNS query or
b. If HOSTNAME(Not IP Address) is configured at the client side, and
in this case DNS query must take place
to find the LDAP Host.
If you are not getting any DNS query then your LDAP client has IP
Address hardcoded for your LDAP Server.
O Plameras
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
