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!

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us for this Tech Talk and learn how to ...

.conf24 | Personalize your .conf experience with Learning Paths!

Personalize your .conf24 Experience Learning paths allow you to level up your skill sets and dive deeper ...

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...