<?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: domain name wrong for MSAD:NT6:DNS in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645237#M109786</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;are you sure that src_domain field contains that DNS domain with (\d)?&lt;/P&gt;&lt;P&gt;This seems to work, so my guess is that that field didn't contain it or it has defined after that eval (see ASCII order)?&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| makeresults 
| eval _raw="(6)mobile(6)events(4)data(9)microsoft(3)com(0)
(5)teams(6)events(4)data(9)microsoft(3)com(0)
(4)pool(3)ntp(3)org(0)" 
| multikv noheader=t
| table _raw
``` Above generate test data ```
| eval fqdn=trim(replace(_raw,"\([0-9]+\)","."),".")&lt;/LI-CODE&gt;&lt;P&gt;Ensure that src_domain EVAL/EXTRACTION etc. has done before you try to do that EVAL-fqdn.&lt;/P&gt;&lt;P&gt;See the execution order &amp;nbsp;for props + transforms&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Searchtimeoperationssequence" target="_self"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Searchtimeoperationssequence&lt;/A&gt;&lt;/P&gt;&lt;P&gt;and remember that those EVAL etc. has executed by ASCII order not the order how they exists in conf files!&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
    <pubDate>Wed, 31 May 2023 11:47:26 GMT</pubDate>
    <dc:creator>isoutamo</dc:creator>
    <dc:date>2023-05-31T11:47:26Z</dc:date>
    <item>
      <title>Why is domain name wrong for MSAD:NT6:DNS?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645216#M109785</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;We have enable windows DNS debug on our AD servers, but get in wrong domain names.&lt;BR /&gt;I have tried on our SH two diffrent prop.conf but still wrong domain names.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;[MSAD:NT6:DNS]&lt;BR /&gt;EVAL-fqdn=trim(replace(src_domain,"\([0-9]+\)","."),".")&lt;BR /&gt;&lt;BR /&gt;[MSAD:NT6:DNS]&lt;BR /&gt;EVAL-src_domain_punct = trim(replace(src_domain, "\(\d+\)", "."),".")&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Example of domain name:&lt;BR /&gt;&lt;SPAN&gt;(6)mobile(6)events(4)data(9)microsoft(3)com(0)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(5)teams(6)events(4)data(9)microsoft(3)com(0)&lt;BR /&gt;(4)pool(3)ntp(3)org(0)&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Can you help advise on how to remove ( ) from the FQDN ?&lt;BR /&gt;&lt;BR /&gt;Thank you in advance&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 15:01:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645216#M109785</guid>
      <dc:creator>janroc</dc:creator>
      <dc:date>2023-05-31T15:01:57Z</dc:date>
    </item>
    <item>
      <title>Re: domain name wrong for MSAD:NT6:DNS</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645237#M109786</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;are you sure that src_domain field contains that DNS domain with (\d)?&lt;/P&gt;&lt;P&gt;This seems to work, so my guess is that that field didn't contain it or it has defined after that eval (see ASCII order)?&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| makeresults 
| eval _raw="(6)mobile(6)events(4)data(9)microsoft(3)com(0)
(5)teams(6)events(4)data(9)microsoft(3)com(0)
(4)pool(3)ntp(3)org(0)" 
| multikv noheader=t
| table _raw
``` Above generate test data ```
| eval fqdn=trim(replace(_raw,"\([0-9]+\)","."),".")&lt;/LI-CODE&gt;&lt;P&gt;Ensure that src_domain EVAL/EXTRACTION etc. has done before you try to do that EVAL-fqdn.&lt;/P&gt;&lt;P&gt;See the execution order &amp;nbsp;for props + transforms&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Searchtimeoperationssequence" target="_self"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Searchtimeoperationssequence&lt;/A&gt;&lt;/P&gt;&lt;P&gt;and remember that those EVAL etc. has executed by ASCII order not the order how they exists in conf files!&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 11:47:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645237#M109786</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2023-05-31T11:47:26Z</dc:date>
    </item>
    <item>
      <title>Re: domain name wrong for MSAD:NT6:DNS</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645242#M109787</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thank for your answer.&lt;/P&gt;&lt;P&gt;Yes I am 100% sure that the src_domain&amp;nbsp;&lt;SPAN&gt;field contains that DNS domain with (\d)&lt;BR /&gt;Can you recommend&amp;nbsp;an working props.conf at search time?&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="janroc_0-1685535013240.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/25627i7B6B0CCC3FD48A6C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="janroc_0-1685535013240.png" alt="janroc_0-1685535013240.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 12:12:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645242#M109787</guid>
      <dc:creator>janroc</dc:creator>
      <dc:date>2023-05-31T12:12:07Z</dc:date>
    </item>
    <item>
      <title>Re: domain name wrong for MSAD:NT6:DNS</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645243#M109788</link>
      <description>&lt;P&gt;Can you share your props.conf for this sourcetype (also if there is some source:: or host::) definition and transforms.conf if you are using those? Please insert those inside &amp;lt;/&amp;gt; block for reading easier.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 12:16:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645243#M109788</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2023-05-31T12:16:29Z</dc:date>
    </item>
    <item>
      <title>Re: domain name wrong for MSAD:NT6:DNS</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645246#M109789</link>
      <description>&lt;P&gt;We have no own props.conf right now, that what I need suggestions for.&lt;BR /&gt;The only props.conf with that sourcetype is from Splunk_TA_windows app at Splunkbase.&lt;BR /&gt;&lt;BR /&gt;[MSAD:NT6:DNS]&lt;BR /&gt;KV_MODE = none&lt;BR /&gt;SHOULD_LINEMERGE = false&lt;BR /&gt;CHECK_FOR_HEADER = false&lt;BR /&gt;EXTRACT-threadid = (?&amp;lt;threadid&amp;gt;[0-9A-Fa-f]+)\s+(?&amp;lt;context&amp;gt;PACKET)&lt;BR /&gt;EXTRACT-protocol = (?&amp;lt;packetid&amp;gt;[0-9A-Fa-f]*) (?&amp;lt;protocol&amp;gt;UDP|TCP) (?&amp;lt;direction&amp;gt;\w+) (?&amp;lt;src_ip&amp;gt;[0-9A-Fa-f\.\:]+)\s+&lt;BR /&gt;EXTRACT-opcode = (?&amp;lt;operation&amp;gt;[ R]) (?&amp;lt;opcode&amp;gt;.) \[(?&amp;lt;hexflags&amp;gt;[0-9A-Fa-f]+) (?&amp;lt;flags&amp;gt;....) (?&amp;lt;response&amp;gt;[^\]]+)\]&lt;BR /&gt;EXTRACT-question1 = \] (?&amp;lt;questiontype&amp;gt;\w+)\s+(?&amp;lt;questionname&amp;gt;.*)&lt;BR /&gt;EXTRACT-question2 = \] (?&amp;lt;questionname&amp;gt;[^\s]*)$&lt;BR /&gt;FIELDALIAS-query = questionname AS query&lt;BR /&gt;FIELDALIAS-reply_code = response AS reply_code&lt;BR /&gt;FIELDALIAS-transaction_id = packetid AS transaction_id&lt;BR /&gt;FIELDALIAS-transport = protocol AS transport&lt;BR /&gt;FIELDALIAS-vendor_query_type = opcode AS vendor_query_type&lt;BR /&gt;REPORT_KV_for_microsoft_dns_web = KV_for_port,KV_for_Domain,KV_for_RecvdIP,KV_for_microsoftdns_action,KV_for_Record_type,KV_for_Record_Class&lt;BR /&gt;LOOKUP-dns_action_lookup = dns_action_lookup vendor_dns_action OUTPUT action&lt;BR /&gt;LOOKUP-dns_vendor_lookup = dns_vendor_lookup sourcetype OUTPUT vendor,product,app&lt;BR /&gt;LOOKUP-dns_recordclass_lookup = dns_recordclass_lookup record_class_number OUTPUT record_class&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 12:43:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645246#M109789</guid>
      <dc:creator>janroc</dc:creator>
      <dc:date>2023-05-31T12:43:36Z</dc:date>
    </item>
    <item>
      <title>Re: domain name wrong for MSAD:NT6:DNS</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645251#M109791</link>
      <description>&lt;P&gt;I have no selfmade props.conf on SH only Splunk_TA_windows app from splunkbase.&lt;BR /&gt;&lt;BR /&gt;[MSAD:NT6:DNS]&lt;BR /&gt;KV_MODE = none&lt;BR /&gt;LINE_BREAKER = ([\r\n]+)(\d{1,2}.\d{1,2}.\d{4} \d{1,2}:\d{1,2}:\d{1,2} \w{2})&lt;BR /&gt;# Load balancing on UF&lt;BR /&gt;EVENT_BREAKER_ENABLE = true&lt;BR /&gt;EVENT_BREAKER = ([\r\n]+)(\d{1,2}.\d{1,2}.\d{4} \d{1,2}:\d{1,2}:\d{1,2} \w{2})&lt;BR /&gt;SHOULD_LINEMERGE = false&lt;BR /&gt;CHECK_FOR_HEADER = false&lt;BR /&gt;EXTRACT-singleLine = (?&amp;lt;threadid&amp;gt;[0-9A-Fa-f]+)\s+(?&amp;lt;context&amp;gt;PACKET)\s+(?&amp;lt;packetid&amp;gt;[0-9A-Fa-f]*) (?&amp;lt;protocol&amp;gt;UDP|TCP) (?&amp;lt;direction&amp;gt;\w+) (?&amp;lt;src_ip&amp;gt;[0-9A-Fa-f\.\:]+)\s+(?&amp;lt;xid&amp;gt;[0-9A-Fa-f]+)\s+(?&amp;lt;operation&amp;gt;[ R]) (?&amp;lt;opcode&amp;gt;.) \[(?&amp;lt;hexflags&amp;gt;[0-9A-Fa-f]+) (?&amp;lt;flags&amp;gt;....) (?&amp;lt;response&amp;gt;[^\]]+)\]\s+(?:QTYPE\s+)?(?&amp;lt;questiontype&amp;gt;\w+)\s+(?:QCLASS\s+\d+\s+)?(:?\(\d+\))?(?&amp;lt;questionname&amp;gt;[^\n]*)\(0\)&lt;BR /&gt;EXTRACT-answer = (ANSWER\s+SECTION|UPDATE\s+SECTION):(?&amp;lt;ANSWER_OR_UPDATE_SECTION&amp;gt;.*?)(AUTHORITY\s+SECTION|ADDITIONAL\s+SECTION)&lt;BR /&gt;EVAL-query = replace(questionname,"(?:\(\d+\))",".")&lt;BR /&gt;FIELDALIAS-record_type = questiontype AS record_type&lt;BR /&gt;FIELDALIAS-query = questionname AS query&lt;BR /&gt;FIELDALIAS-src=src_ip AS src&lt;BR /&gt;FIELDALIAS-dest = host AS dest&lt;BR /&gt;FIELDALIAS-transaction_id = packetid AS transaction_id&lt;BR /&gt;FIELDALIAS-transport = protocol AS transport&lt;BR /&gt;FIELDALIAS-vendor_query_type = opcode AS vendor_query_type&lt;BR /&gt;EVAL-message_type = if(operation=="R","Response", "Query")&lt;BR /&gt;EVAL-name = if(operation=="R","R","")+opcode+"_"+response+"_"+questiontype&lt;BR /&gt;EVAL-answer = mvmap(answer, replace(replace(answer,"\(\d+\)","."),"\\[\\w+\\]",""))&lt;BR /&gt;EVAL-vendor_product = "Microsoft Windows"&lt;BR /&gt;REPORT-Multi_answer = Answer_multi_value&lt;BR /&gt;REPORT-KV_for_microsoft_dns_web = KV_for_port,KV_for_Domain,KV_for_microsoftdns_action,KV_for_Record_type,KV_for_Record_Class,KV_for_Answer_Section_Count,KV_for_Update_Section_Count&lt;BR /&gt;LOOKUP-windows_dns_query_type_lookup = windows_dns_query_type_lookup opcode OUTPUT query_type&lt;BR /&gt;LOOKUP-windows_dns_action_lookup = windows_dns_action_lookup message_type,vendor_dns_action OUTPUT action,reply_code,reply_code_id&lt;BR /&gt;LOOKUP-dns_recordclass_lookup = dns_recordclass_lookup record_class_number OUTPUT record_class&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 12:57:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645251#M109791</guid>
      <dc:creator>janroc</dc:creator>
      <dc:date>2023-05-31T12:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: domain name wrong for MSAD:NT6:DNS</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645253#M109792</link>
      <description>&lt;P&gt;src_domain hasn't defined on those props.conf but there seems to be couple of transforms defined. Can you also &lt;EM&gt;&lt;STRONG&gt;add those inside &amp;lt;/&amp;gt; block,&lt;/STRONG&gt;&lt;/EM&gt; so we can be ensure that those are exactly what you have on your side!&lt;/P&gt;&lt;P&gt;Needed transforms (at least):&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Answer_multi_value&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;KV_for_port&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;KV_for_Domain&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;KV_for_microsoftdns_action&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;KV_for_Record_type&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;KV_for_Record_Class&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;KV_for_Answer_Section_Count&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;KV_for_Update_Section_Count&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;KV_for_RecvdIP&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;What is your splunk version and also those TA versions? Are you running it on linux or in windows?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You have posted two props.conf definition for MSAD:NT7:DNS which one is on use? You could check it with b&lt;/SPAN&gt;tools.&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 13:14:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645253#M109792</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2023-05-31T13:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: domain name wrong for MSAD:NT6:DNS</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645254#M109793</link>
      <description>&lt;P&gt;I hade version 7.0.0 on the SH and upgraded to 8.7.0 but it didn't change anything for my problem.&lt;BR /&gt;I tried two props.conf but was not using any of them.&lt;BR /&gt;&lt;BR /&gt;But I found an new props.conf on the community and now the query field is working, so I guess we can use this field.&lt;BR /&gt;&lt;BR /&gt;[MSAD:NT6:DNS]&lt;BR /&gt;SEDCMD-win_dns-first = s/\(\d+\)/./g&lt;BR /&gt;SEDCMD-win_dns-second = s/\s\.(.*)\.$/ \1/g&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 13:20:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-domain-name-wrong-for-MSAD-NT6-DNS/m-p/645254#M109793</guid>
      <dc:creator>janroc</dc:creator>
      <dc:date>2023-05-31T13:20:43Z</dc:date>
    </item>
  </channel>
</rss>

