<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DNS Resolution in a search in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89171#M22862</link>
    <description>&lt;P&gt;If performance is an issue with dnslookup, which can happen when you have many distinct ips being returned by your search, you may want to populate your own lookup and refresh it nightly when there is less demand for resources. Here's a search I run nightly against a week of Windows security event log data to get the ips of machines that have been logged into, but you could substitute your own search for a list of ips to look up: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype=wineventlog:security EventCode=4768 NOT src_ip="::1"
| eval ip=replace(src_ip,"[f:]","") 
| dedup ip 
| lookup dnslookup clientip as ip OUTPUTNEW clienthost as hostname 
| table ip, hostname
| outputlookup ip2host.csv
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 14 Mar 2017 17:00:52 GMT</pubDate>
    <dc:creator>tibbian</dc:creator>
    <dc:date>2017-03-14T17:00:52Z</dc:date>
    <item>
      <title>DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89161#M22852</link>
      <description>&lt;P&gt;Is it possible to have ip addresses in a search resolved to a host name and displayed in the results rather then the ip address.  My search is:&lt;/P&gt;

&lt;P&gt;source="udp:514" "dst=192.168." | stats count by dst | sort -count limit=10&lt;/P&gt;

&lt;P&gt;This gives me the top ten hit ip addresses.  I would like to see the host name rather than (or as well as) the ip address.  Can this be done as part of the search string?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2013 21:59:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89161#M22852</guid>
      <dc:creator>balcv</dc:creator>
      <dc:date>2013-10-08T21:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89162#M22853</link>
      <description>&lt;P&gt;Read the following:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/answers/8051/dns-lookup-via-splunk"&gt;http://answers.splunk.com/answers/8051/dns-lookup-via-splunk&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;and&lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/answers/103154/dns-lookup-for-ip-address-in-log-meesage"&gt;http://answers.splunk.com/answers/103154/dns-lookup-for-ip-address-in-log-meesage&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Those should do it for you!&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2013 22:02:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89162#M22853</guid>
      <dc:creator>jtrucks</dc:creator>
      <dc:date>2013-10-08T22:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89163#M22854</link>
      <description>&lt;P&gt;Yes.  But you will need a lookup table that matches the IP address to the host name.  &lt;/P&gt;

&lt;P&gt;Depending on the apps you have installed, you may find that this lookup table already exists.  If it does already exist you will find it in the lookup folder, and it will automatically populate a field in which case you simply need to add the field to your stats.  The name of the field escapes me.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2013 22:03:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89163#M22854</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2013-10-08T22:03:54Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89164#M22855</link>
      <description>&lt;P&gt;Actually, the answers entries I linked to are for using an external command that performs the lookup on the fly and responds with the results.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2013 22:43:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89164#M22855</guid>
      <dc:creator>jtrucks</dc:creator>
      <dc:date>2013-10-08T22:43:38Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89165#M22856</link>
      <description>&lt;P&gt;You answered at the same time I did.  Besides, if they are already there...&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2013 23:09:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89165#M22856</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2013-10-08T23:09:53Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89166#M22857</link>
      <description>&lt;P&gt;The transforms.conf files did the trick and with a little manipulation of the search I have the results I wanted.&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2013 23:13:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89166#M22857</guid>
      <dc:creator>balcv</dc:creator>
      <dc:date>2013-10-08T23:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89167#M22858</link>
      <description>&lt;P&gt;There is no need to create a lookup table as long as the nameserver holds those records. Just use the following after your example search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;search&amp;gt; | lookup dnslookup clientip as dst OUTPUT clienthost as DST_RESOLVED
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 15 Nov 2013 23:12:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89167#M22858</guid>
      <dc:creator>pryzrak</dc:creator>
      <dc:date>2013-11-15T23:12:47Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89168#M22859</link>
      <description>&lt;P&gt;perfect, thanks for this solution - works perfectly&lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2016 00:20:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89168#M22859</guid>
      <dc:creator>johnsond</dc:creator>
      <dc:date>2016-05-11T00:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89169#M22860</link>
      <description>&lt;P&gt;You should click "Accept" to close the question.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jan 2017 16:29:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89169#M22860</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-01-16T16:29:32Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89170#M22861</link>
      <description>&lt;P&gt;this query has worked for me "lookup dnslookup clientip as lsp_rro OUTPUT clienthost as hops"  when trying to make a human readable LSP path.  We use /etc/hosts for the IP to hostname lookup, you can also use a DNS server to fill this requirement such as BIND9, MS Server or dnsmasq to name a few.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jan 2017 19:48:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89170#M22861</guid>
      <dc:creator>johnsond</dc:creator>
      <dc:date>2017-01-16T19:48:11Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Resolution in a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89171#M22862</link>
      <description>&lt;P&gt;If performance is an issue with dnslookup, which can happen when you have many distinct ips being returned by your search, you may want to populate your own lookup and refresh it nightly when there is less demand for resources. Here's a search I run nightly against a week of Windows security event log data to get the ips of machines that have been logged into, but you could substitute your own search for a list of ips to look up: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype=wineventlog:security EventCode=4768 NOT src_ip="::1"
| eval ip=replace(src_ip,"[f:]","") 
| dedup ip 
| lookup dnslookup clientip as ip OUTPUTNEW clienthost as hostname 
| table ip, hostname
| outputlookup ip2host.csv
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 14 Mar 2017 17:00:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DNS-Resolution-in-a-search/m-p/89171#M22862</guid>
      <dc:creator>tibbian</dc:creator>
      <dc:date>2017-03-14T17:00:52Z</dc:date>
    </item>
  </channel>
</rss>

