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.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Request for Professional Development: Attending .conf26

Winning Over the Boss: Your Pass to .conf26 conf26 is going to be here before you know it. If don't already ...