Hi @AD ,
I'm making the assumption that you are using Microsoft AD LDS (ADAM) for your LDAP environment.
I've tested using LDP with IPv6 binding and connecting to a local LDAP instance without any issues.
and a ldap_search_s command is successful in returning records:
The same is true if I connect remotely as well
and the search works
I'm assuming you change the BaseDN and Objectclass details in your question but to help remove any typos, use the dropdown option on the search dialog to select the base DN of your LDAP instance, as shown below.
From the testing I've done, yes AD LDS is able to support IPv6 connection and searches without issuing a referral for objects that exist in the context. Normally a referral is issue if the object is not within the context, but the LDAP server knows where it exists and provides the referral to the call client for information. You could try enabling referral as Session Option to the LDS server and see if this resolve the issue.
Within LDP from the Options menu, select Connection Options, and set the option as shown below, this will cause the server to chase the internal referral and return the results if they are within the same context:
You could also try setting the LDAP_OPT_REFERRALS = 64, which will cause the server to chase external referrals.
If that doesn't work maybe if you can share the RootDSE of the LDAP instance, any CrossRef objects that have been created, and the search details you are searching for.
Gary.