FQDN not working for LDAP connection (IP works)

InsightConnect
,
1

Issue: FQDN not working for LDAP connection (IP works)

Hi everyone,

I’m encountering an issue with the Active Directory LDAP plugin in InsightConnect.

  • When I configure the connection using the server hostname (FQDN), it fails with the error below:

    …insightconnect_plugin_runtime.exceptions.PluginException: An error occurred during plugin execution! The service this plugin is designed for is currently unavailable. Try again later. If the issue persists, please contact support. Response was: invalid server address.

  • However, when I use the IP address of the domain controller, the connection works successfully.

Troubleshooting done

From the orchestrator server, I tested name resolution:

  • IP address → works

  • FQDN → resolves correctly

  • Short hostname → resolves correctly

So DNS resolution from the server itself appears to be functioning properly.

:thinking: Observation

Since DNS lookups work at the OS level but fail within the plugin, it seems the issue may be related to:

  • How InsightConnect is handling or transforming the FQDN input, or

  • A limitation/validation issue within the LDAP plugin runtime

Question

Has anyone experienced a similar issue where:

  • FQDN fails but IP works in InsightConnect LDAP plugin?

  • If so, was it related to formatting, connection settings, or a known bug?

Any insights or suggestions would be appreciated!

2

It would be docker that is failing to resolve the domain. What OS are you using, and how did you configure your IP and DNS on the server? Is this a new orchestrator that has been stood up and configured without restarting the orchestrator/docker services?