[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: DNS configuration

To: "Howard Chu" <hyc@symas.com>
Subject: Re: DNS configuration
From: "Hai Zaar" <haizaar@gmail.com>
Date: Mon, 11 Sep 2006 12:07:47 +0300
Cc: OpenLDAP-software@OpenLDAP.org
Content-disposition: inline
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jgzoZqkh2Plaf6G5EC7Cpuih4774H3Im0oLxjtp/nqmLrC/uBPKhCwZzrthUwYWV98ohx6MSoT9DSzi2kENUrJU7ewJfCL3XDG0ZhDpmhtG0aWIurNv2BlK3p5J6qqTBni1i+Gpm0lafuyywi5Sy3BPGqEqLfbjSWQrH7Il/TT4=
In-reply-to: <45052513.4000009@symas.com>
References: <cfb54190609110115u356e50cdk218e5b5a4ef450bf@mail.gmail.com> <45052513.4000009@symas.com>

Hm, what does this question have to do with OpenLDAP software?

ldapsearch knows nothing about DNS or Kerberos. The behavior you're
seeing is Kerberos-specific, and has nothing to do with LDAP or OpenLDAP
software.

You are right. With simple bind (-x) ldapsearch does not do any of the
reverse lookups. The behavior I've described probably comes from SASL.

Thanks
--
Zaar

References:
- DNS configuration
  - From: "Hai Zaar" <haizaar@gmail.com>
- Re: DNS configuration
  - From: Howard Chu <hyc@symas.com>

Prev by Date: Re: DNS configuration
Next by Date: Re: DNS configuration
Index(es):
- Chronological
- Thread