<?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 dnsproxy failures in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dnsproxy-failures/m-p/38086#M27890</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;System log fills with messages like "Failed to resolve domain name:defrxpwgklm.capco.com after trying all attempts to name server(s): 8.8.4.4&amp;nbsp; 194.25.0.68". DNS without dnsproxy is working. Can i restart the dnsproxy to fix this issue?&lt;/P&gt;&lt;P&gt;The messages are appearing after some threats of type "&lt;SPAN style="color: #000000; font-family: Tahoma, Arial, Helvetica, sans-serif; font-size: 11px; background-color: #ffffff;"&gt;Suspicious DNS Query&lt;/SPAN&gt;".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Mar 2013 10:02:41 GMT</pubDate>
    <dc:creator>azwicker</dc:creator>
    <dc:date>2013-03-21T10:02:41Z</dc:date>
    <item>
      <title>dnsproxy failures</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dnsproxy-failures/m-p/38086#M27890</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;System log fills with messages like "Failed to resolve domain name:defrxpwgklm.capco.com after trying all attempts to name server(s): 8.8.4.4&amp;nbsp; 194.25.0.68". DNS without dnsproxy is working. Can i restart the dnsproxy to fix this issue?&lt;/P&gt;&lt;P&gt;The messages are appearing after some threats of type "&lt;SPAN style="color: #000000; font-family: Tahoma, Arial, Helvetica, sans-serif; font-size: 11px; background-color: #ffffff;"&gt;Suspicious DNS Query&lt;/SPAN&gt;".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 10:02:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dnsproxy-failures/m-p/38086#M27890</guid>
      <dc:creator>azwicker</dc:creator>
      <dc:date>2013-03-21T10:02:41Z</dc:date>
    </item>
    <item>
      <title>Re: dnsproxy failures</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dnsproxy-failures/m-p/38087#M27891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Which version Panos you use ?&lt;/P&gt;&lt;P&gt;you use dns proxy on PaloAlto ? you tried to restart ,did it solve ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2013 19:55:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dnsproxy-failures/m-p/38087#M27891</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2013-03-29T19:55:31Z</dc:date>
    </item>
    <item>
      <title>Re: dnsproxy failures</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dnsproxy-failures/m-p/38088#M27892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I wouldnt be suprised if defrxpwgklm.capco.com is a malware url, I have seen similar design of the subdomain part which previously have been classified as malware-related.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also currently it doesnt seem to resolve at all:&lt;/P&gt;&lt;P&gt;;; QUESTION SECTION:&lt;/P&gt;&lt;P&gt;;defrxpwgklm.capco.com.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ANY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;;; AUTHORITY SECTION:&lt;/P&gt;&lt;P&gt;capco.com.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3600&amp;nbsp;&amp;nbsp;&amp;nbsp; IN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SOA&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ns1.netnames.net. hostmaster.net&lt;/P&gt;&lt;P&gt;names.net. 2013032800 10800 1800 3600000 21600&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2013 21:43:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dnsproxy-failures/m-p/38088#M27892</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-03-29T21:43:28Z</dc:date>
    </item>
    <item>
      <title>Re: dnsproxy failures</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dnsproxy-failures/m-p/78193#M42856</link>
      <description>&lt;P&gt;Old thread, but as it is still visible - from description it seems to be matching scenario described in following KB article:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Management-Articles/Blocking-Suspicious-DNS-Queries-with-DNS-Proxy-Enabled/ta-p/66037" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Management-Articles/Blocking-Suspicious-DNS-Queries-with-DNS-Proxy-Enabled/ta-p/66037&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2016 08:11:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dnsproxy-failures/m-p/78193#M42856</guid>
      <dc:creator>phrdlicka</dc:creator>
      <dc:date>2016-05-17T08:11:05Z</dc:date>
    </item>
  </channel>
</rss>

