All Apps and Add-ons

DsBind failed

adamblock1
Explorer

A few days I upgraded my Splunk servers (Deployment/license server, search head, indexers, heavy forwarder) from version 5.0.5 to 5.0.8. While reviewing the splunkd.log file on one of the indexer servers, I noticed a large number of warnings which state "WinEventLogChannel - connectToDC: DsBind failed: (1722)'No such host is known.'"

The indexer appears to be receiving logs properly.

Any assistance would be appreciated.

Thank you.

Tags (1)
0 Karma

chanfoli
Builder

If you are seeing these errors with a basic event logging setup and you don't have your universal forwarders talking to AD to resolve AD objects in events, you might want to try this in your inputs.conf:

evt_resolve_ad_obj = 0

This tells the forwarder not to try to resolve AD objects. The default with this input type is to do so but if you don't set up the AD binding with evt_dc_name or evt_dns_name it does not work so you will see tons of these errors.

Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk on November 6 at 11AM PT, and empower your SOC to reach new heights! Duration: ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...