Hi all,
First of all, I don't know whether if this is a bug and I don't know where to submit a bug.

My 389ds info:
OS: CentOS Linux release 7.6.1810 (Core)
389ds: 389-ds-base-1.3.8.4-15.el7.x86_64

On 389ds server, I have configured like this
# auto.master, service, example.com
dn: nismapname=auto.master,ou=service,dc=example,dc=com
nisMapName: auto.master
objectClass: nisMap
objectClass: top

# /home, auto.master, service, example.com
dn: cn=/home,nismapname=auto.master,ou=service,dc=example,dc=com
nisMapName: home
objectClass: nisObject
objectClass: top
cn: /home
nisMapEntry: ldap 389ds.example.com

# *, auto.home, service, example.com
dn: cn=*,nismapname=auto.home,ou=service,dc=example,dc=com
nisMapName: home
nisMapEntry: -fstype=nfs4,defaults,_netdev,acl  sun:/home/&
objectClass: nisObject
objectClass: top
cn: *:nismapname=auto.home,ou=service,dc=example,dc=com


On client side
When I want to change directory under home (cd /home/username), I can't.
So I enable the autofs debug mode, and I see some message like this

Aug 22 15:55:36 centos automount[2424]: parse_server_string: lookup(ldap): server "ldap://ds.example.com/", base dn "nismapname=auto.home,ou=service,dc=example,dc=com"

The prefix 389 has gone. The client says can't connect LDAP server because in 389ds server I write ldap 389ds.example.com but I see ds.example.com on client-side.

I don't know whether this is a bug. Just write this to let you know. Thanks!


My solution is:
change the 389ds server-side using nisMapEntry: ldap tc-389ds.example.com.



Sincerely,
--
DaV