While updating the LDAP domain information, system throws below error:

"Service Failure: ServerError: Can not update domain information for domain abcd1. [95505011]"
 

Caused by: javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: DomainDnsZones.abcd1.ad.abcd4.com:389 [Root exception is java.net.ConnectException: Connection timed out: connect]]
	at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(Unknown Source)
	at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(Unknown Source)
	at com.compositesw.server.security.DefaultLdapDomainConnection.searchWithPagedResultsControl(DefaultLdapDomainConnection.java:499)
	at com.compositesw.server.security.DefaultLdapDomainConnection.getSingleValuesForParams(DefaultLdapDomainConnection.java:955)
	at com.compositesw.server.security.DefaultLdapDomainConnection.getAllGroups(DefaultLdapDomainConnection.java:442)
	... 45 more
Caused by: javax.naming.CommunicationException: DomainDnsZones.bp1.ad.bp.com:389 [Root exception is java.net.ConnectException: Connection timed out: connect]
	at com.sun.jndi.ldap.LdapReferralContext.<init>(Unknown Source)
	at com.sun.jndi.ldap.LdapReferralException.getReferralContext(Unknown Source)
	at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreReferrals(Unknown Source)

As per : https://confluence.atlassian.com/crowdkb/user-lookups-fail-with-partialresultexceptions-140181770.html suggestion, changing the LDAP port to global catalog port on 3268 instead of 389 (Global Catalogs does not tell the client to chase down referrals) will fix the issue. Now URL has been updated successfully.