Security

AD Auth fails if /etc/resolv.conf is present

Sqig
Path Finder

Hi. We have successfully enabled Active Directory/LDAP Authentication in Splunk 4.1.3.

All works as expected.

However, when we have /etc/resolv.conf in place, logins never complete. Hitting the submit button results in a permanent "waiting for (search head)"

We have the LDAP server in authentication.conf specified by IP, so no lookup should be required.

The nameserver is responsive, if that matters.

Has anyone run across this problem?

Tags (2)
0 Karma

JSapienza
Contributor

I personally haven't seen this issue. I have setup AD auth serveral times and not had an issues.And it works just fine with the resolve.conf .
Maybe there was/is a problem with your resolve.conf ?

Did you happen have the "search" option set to your domain ?

Example:

search myDomain.local

nameserver 10.10.100.100

What did splunkd.log say ? You might want to enable debug in log.cfg is you are not seeing any specifics. http://www.splunk.com/wiki/Community:EnableDebugLogging

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...