On 07.03.2013 20:39, Paul Muster wrote: > On 07.03.2013 20:06, Andreas Metzler wrote: > >> Just for debugging, does it work if you specify the IP address of the >> ldap server instead of its name? > > That works!!11 Great, after weeks of research - it works! > > But why? DNS is ok: > > # su Debian-exim > \h:\w$ nslookup ldap > Server: 192.168.1.1 > Address: 192.168.1.1#53 > > Name: ldap.domain.tld > Address: 192.168.1.8 > > \h:\w$ host ldap > ldap.domain.tld has address 192.168.1.8 > \h:\w$
nslookup and host are successful while dig fails: # su Debian-exim \h:\w$ dig ldap ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> ldap ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51789 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;ldap. IN A ;; AUTHORITY SECTION: . 4051 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2013030701 1800 900 604800 86400 ;; Query time: 0 msec ;; SERVER: 192.168.1.254#53(192.168.1.254) ;; WHEN: Thu Mar 7 21:01:44 2013 ;; MSG SIZE rcvd: 97 \h:\w$ Accordingly ist also works when putting LDAP server's FQDN in Exim authenticator. But why? # cat /etc/resolv.conf domain domain.tld search domain.tld nameserver 192.168.1.1 Thanks & greetings, Paul
smime.p7s
Description: S/MIME Cryptographic Signature
