Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- Re: dns resolving in search failed
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
dns resolving in search failed
Hi Splunkers
Using syslog output from Netfilter/Iptables.
Reading it into Splunk, but cant get IP resolved to DNS.
Tried several links available.
http://answers.splunk.com/answers/61853/resolve-ip-address
http://answers.splunk.com/answers/30075/dns-lookup-failing
http://answers.splunk.com/answers/8051/dns-lookup-via-splunkAlso tried Iptable and Lookup plugins
No luck: whats next ?
Would appreciate a fine Firewall dashboard, maybe there is a better solution around ?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Should not be complicated:
I get a list of IPnrs form the remote syslog, fine, but whatever I try, nameresolution fails.
It remains a list of IPnumber, I like to see names.
Ihe links I mentioned deal with this issue, but no go here.
What else to try ?
(Even beter: a dashboard for Netfilter/IpTables, with graphs and all, but the ones available dont work properly. Ill get to that later.)
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There, I fixed it. Case of RTFM, and proper field names. Also sorted the columns. Nice.
host="192.168.x.x" | lookup dnslookup clientip as DST OUTPUT clienthost as DST_RESOLVED | lookup dnslookup clientip as SRC OUTPUT clienthost as SRC_RESOLVED | Table _time SRC SRC_RESOLVED DST DST_RESOLVED PROTO DPT
Digging in Netfilter-Iptables after this.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just post an EXAMPLE of what doesn't work. Stop keep describing it and SHOW us. And post it in your question, not as an answer, which it is not.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You would be better off posting an example of specifically what does not work, rather than a non-specific "can't get to work".
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas
What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)
Automating Threat Operations and Threat Hunting with Recorded Future
