[JENKINS-71511] LDAPS tries to connect to DomainDnsZones instead of specified Server

LDAPS tries to connect to DomainDnsZones instead of specified server

Without ldaps it works fine, but with ldaps://servername:636 the following error is returned

 

java.net.ConnectException: Connection timed out: connect

Caused: javax.naming.CommunicationException: DomainDnsZones.*:636 [Root exception is java.net.ConnectException: Connection timed out: connect]

---
Originally reported by loojo, imported from: LDAPS tries to connect to DomainDnsZones instead of specified Server

• status: Open
  
• priority: Major
  
• component(s): ldap-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-09
  

Raw content of original issue

LDAPS tries to connect to DomainDnsZones instead of specified server


Without ldaps it works fine, but with ldaps://servername:636 the following error is returned


 


java.net.ConnectException: Connection timed out: connect

Caused: javax.naming.CommunicationException: DomainDnsZones.*:636 [Root exception is java.net.ConnectException: Connection timed out: connect]

environment

```
Jenkins 2.387.3

LDAP Plugin Version 682.v7b_544c9d1512
```

1 attachment

- [image-2023-06-21-22-22-24-939.png](https://issues.jenkins.io/secure/attachment/60634/image-2023-06-21-22-22-24-939.png)
> 

No file or test is named. Start by reproducing the issue with Jenkins 2.387.3 and LDAP Plugin 682.v7b_544c9d1512, comparing ldaps://servername:636 with the working non-LDAPS path. Trace why the connection target becomes DomainDnsZones; done means LDAPS connects to the specified server and the behavior has regression coverage.

Written by the indexing model from the issue text.