Hi,
it turns out, named is not recognising /etc/ldap.conf, /usr/local/etc/ldap.conf or /usr/local/etc/openldap/ldap.conf. Am I missing something? It's not running as chroot:
on LDAP side it clearly states that it is not doing a starttls:
All other TLS/SSL connections to LDAP work fine. My ldap.conf is definitely fine. I just don't know where named is looking for it?! With sshd I needed to do something like this, to get ssh pub keys working from LDAP:
But where would I place this?
it turns out, named is not recognising /etc/ldap.conf, /usr/local/etc/ldap.conf or /usr/local/etc/openldap/ldap.conf. Am I missing something? It's not running as chroot:
Code:
cat /etc/rc.conf
[...]
named_enable="YES"
named_conf="/usr/local/etc/namedb/named.conf"
[...]
on LDAP side it clearly states that it is not doing a starttls:
Code:
Nov 1 21:15:31 FreeBSD slapd[30750]: conn=1058 op=0 BIND dn="cn=admin,dc=DOMAIN,dc=TLD" method=128
Nov 1 21:15:31 FreeBSD slapd[30750]: conn=1058 op=0 RESULT tag=97 err=13 text=confidentiality required
Code:
root@Prod-DNS-1 [~]$ ls -lach {/usr/local/etc/openldap/ldap.conf,/usr/local/etc/ldap.conf,/etc/ldap.conf}
lrwxr-xr-x 1 root wheel 33B Nov 1 21:01 /etc/ldap.conf -> /usr/local/etc/openldap/ldap.conf
lrwxr-xr-x 1 root wheel 33B Nov 1 20:12 /usr/local/etc/ldap.conf -> /usr/local/etc/openldap/ldap.conf
-rwxrwxr-x 1 root wheel 921B Nov 1 21:29 /usr/local/etc/openldap/ldap.conf
All other TLS/SSL connections to LDAP work fine. My ldap.conf is definitely fine. I just don't know where named is looking for it?! With sshd I needed to do something like this, to get ssh pub keys working from LDAP:
Code:
LDAPCONF='/usr/local/etc/openldap/ldap.conf'
export LDAPCONF
export PATH=${PATH}:/usr/local/bin
But where would I place this?