<?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 DNS aged-out, tcp-rst-from-client, and tcp-fin in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dns-aged-out-tcp-rst-from-client-and-tcp-fin/m-p/133748#M47915</link>
    <description>&lt;P&gt;I'm pretty new to Palo Alto products, and I just inherited one. &amp;nbsp;I was having some small issues getting to a site (just a minute or two delay). &amp;nbsp;When I went to the Monitor tab, and saw something that looked a little strange, but could be completely normal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DNSage-outEdit.png" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/6967i3762CB138108A214/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="DNSage-outEdit.png" alt="DNSage-outEdit.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are a lot of these every second. &amp;nbsp;Is it normal for a DNS to go to aged-out or tcp-rst-from-client, or tcp-fin after it returns the information requested? &amp;nbsp;Or is this a sign of something else being wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 20 Dec 2016 17:06:32 GMT</pubDate>
    <dc:creator>JohnCSteamer</dc:creator>
    <dc:date>2016-12-20T17:06:32Z</dc:date>
    <item>
      <title>DNS aged-out, tcp-rst-from-client, and tcp-fin</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-aged-out-tcp-rst-from-client-and-tcp-fin/m-p/133748#M47915</link>
      <description>&lt;P&gt;I'm pretty new to Palo Alto products, and I just inherited one. &amp;nbsp;I was having some small issues getting to a site (just a minute or two delay). &amp;nbsp;When I went to the Monitor tab, and saw something that looked a little strange, but could be completely normal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DNSage-outEdit.png" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/6967i3762CB138108A214/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="DNSage-outEdit.png" alt="DNSage-outEdit.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are a lot of these every second. &amp;nbsp;Is it normal for a DNS to go to aged-out or tcp-rst-from-client, or tcp-fin after it returns the information requested? &amp;nbsp;Or is this a sign of something else being wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Dec 2016 17:06:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-aged-out-tcp-rst-from-client-and-tcp-fin/m-p/133748#M47915</guid>
      <dc:creator>JohnCSteamer</dc:creator>
      <dc:date>2016-12-20T17:06:32Z</dc:date>
    </item>
    <item>
      <title>Re: DNS aged-out, tcp-rst-from-client, and tcp-fin</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-aged-out-tcp-rst-from-client-and-tcp-fin/m-p/135529#M47916</link>
      <description>&lt;P&gt;Hi John&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the case of DNS this is&amp;nbsp;normal as DNS is a UDP protocol which has no means of terminating a session other than no longer transferring packets (where TCP can send FIN or RST packets)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The rst-from-client packets may be your client timing out and deciding to give up gracefully by sending a rst to the server&lt;/P&gt;
&lt;P&gt;Since there is a delay I'd recommend setting up a packetcapture to see if you can detect where packets may be getting lost or where a delay me be introduced&lt;/P&gt;
&lt;P&gt;please take a look at this article to get you started:&amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/Featured-Articles/Getting-Started-Packet-Capture/ta-p/72069" target="_blank"&gt;Getting Started: Packet Capture &lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For future reference: you posted your question in the community feedback forum. You'll reach a much wider audience (all of our other customers, partners, Palo Alto Networks staff etc), if you post questions in the &lt;A href="https://live.paloaltonetworks.com/t5/General-Topics/bd-p/members_discuss" target="_blank"&gt;general forum&lt;/A&gt; &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="general forum.png"&gt;&lt;img src="https://live.paloaltonetworks.com/skins/images/B81F31A7B44084F326ABA63EFCA50C9D/responsive_peak/images/image_not_found.png" alt="general forum.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2017 14:16:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-aged-out-tcp-rst-from-client-and-tcp-fin/m-p/135529#M47916</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-01-03T14:16:09Z</dc:date>
    </item>
    <item>
      <title>Re: DNS aged-out, tcp-rst-from-client, and tcp-fin</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-aged-out-tcp-rst-from-client-and-tcp-fin/m-p/138212#M47917</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Just to let you know that I moved this article to the General Topics area.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2017 22:02:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-aged-out-tcp-rst-from-client-and-tcp-fin/m-p/138212#M47917</guid>
      <dc:creator>jdelio</dc:creator>
      <dc:date>2017-01-18T22:02:09Z</dc:date>
    </item>
  </channel>
</rss>

