<?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 Interpretting Logs on the Firewall in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185958#M361869</link>
    <description>&lt;P&gt;Hi Guys&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope you can help me with this. This is kinda weird.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In our company, we have our agent's tools going over mpls vpn. Our client recently changed the IP of their servers to 2.2.2.2 (IP has been changed). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I check the dns records using client's dns server, let's say for client.com, it resolves to:&lt;/P&gt;&lt;P&gt; 3.3.3.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But other centers are claiming that their dns query resolves to:&lt;/P&gt;&lt;P&gt; 2.2.2.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When i ping client.com, it pings 2.2.2.2. I can successfully access the site, but i'm confused why it shows a different address using nslookup in cmd prompt.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are the logs of the firewall:&lt;/P&gt;&lt;P&gt; client dns server: 10.248.20.200&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA5585# sh log | i 10.249.102.230&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Logging to inside 10.249.102.230 errors: 121&amp;nbsp; dropped: 349&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:43 ASA : %ASA-6-302016: Teardown UDP connection 173519597 for outside:10.248.20.200/53 to inside:10.249.102.230/32809 duration 0:00:00 bytes 153&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:43 ASA : %ASA-6-302013: Built outbound TCP connection 173520593 for outside:1.1.1.1/80 (1.1.1.1/80) to inside:10.249.102.230/48850 (10.249.102.230/48850)&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:44 ASA : %ASA-6-302013: Built outbound TCP connection 173520691 for outside:3.3.3.3/80 (3.3.3.3/80) to inside:10.249.102.230/48994 (10.249.102.230/48994)&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:44 ASA : %ASA-6-302014: Teardown TCP connection 173520691 for outside:3.3.3.3/80 to inside:10.249.102.230/48994 duration 0:00:00 bytes 110 TCP Reset-O&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:45 ASA : %ASA-6-302013: Built outbound TCP connection 173520840 for outside:3.3.3.3/80 (3.3.3.3/80) to inside:10.249.102.230/49186 (10.249.102.230/49186)&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:45 ASA : %ASA-6-302014: Teardown TCP connection 173520840 for outside:3.3.3.3/80 to inside:10.249.102.230/49186 duration 0:00:00 bytes 110 TCP Reset-O&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:57 ASA : %ASA-6-302013: Built outbound TCP connection 173523129 for outside:2.2.2.2/8585 (2.2.2.2/8585) to inside:10.249.102.230/52781 (10.249.102.230/52781)&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:58 ASA : %ASA-6-302013: Built outbound TCP connection 173523287 for outside:3.3.3.3/80 (3.3.3.3/80) to inside:10.249.102.230/53036 (10.249.102.230/53036)&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:59 ASA : %ASA-6-302014: Teardown TCP connection 173523287 for outside:3.3.3.3/80 to inside:10.249.102.230/53036 duration 0:00:00 bytes 110 TCP Reset-O&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 01:01:49 GMT</pubDate>
    <dc:creator>n3tw0rkguy83</dc:creator>
    <dc:date>2019-03-12T01:01:49Z</dc:date>
    <item>
      <title>Interpretting Logs on the Firewall</title>
      <link>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185958#M361869</link>
      <description>&lt;P&gt;Hi Guys&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope you can help me with this. This is kinda weird.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In our company, we have our agent's tools going over mpls vpn. Our client recently changed the IP of their servers to 2.2.2.2 (IP has been changed). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I check the dns records using client's dns server, let's say for client.com, it resolves to:&lt;/P&gt;&lt;P&gt; 3.3.3.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But other centers are claiming that their dns query resolves to:&lt;/P&gt;&lt;P&gt; 2.2.2.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When i ping client.com, it pings 2.2.2.2. I can successfully access the site, but i'm confused why it shows a different address using nslookup in cmd prompt.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are the logs of the firewall:&lt;/P&gt;&lt;P&gt; client dns server: 10.248.20.200&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA5585# sh log | i 10.249.102.230&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Logging to inside 10.249.102.230 errors: 121&amp;nbsp; dropped: 349&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:43 ASA : %ASA-6-302016: Teardown UDP connection 173519597 for outside:10.248.20.200/53 to inside:10.249.102.230/32809 duration 0:00:00 bytes 153&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:43 ASA : %ASA-6-302013: Built outbound TCP connection 173520593 for outside:1.1.1.1/80 (1.1.1.1/80) to inside:10.249.102.230/48850 (10.249.102.230/48850)&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:44 ASA : %ASA-6-302013: Built outbound TCP connection 173520691 for outside:3.3.3.3/80 (3.3.3.3/80) to inside:10.249.102.230/48994 (10.249.102.230/48994)&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:44 ASA : %ASA-6-302014: Teardown TCP connection 173520691 for outside:3.3.3.3/80 to inside:10.249.102.230/48994 duration 0:00:00 bytes 110 TCP Reset-O&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:45 ASA : %ASA-6-302013: Built outbound TCP connection 173520840 for outside:3.3.3.3/80 (3.3.3.3/80) to inside:10.249.102.230/49186 (10.249.102.230/49186)&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:45 ASA : %ASA-6-302014: Teardown TCP connection 173520840 for outside:3.3.3.3/80 to inside:10.249.102.230/49186 duration 0:00:00 bytes 110 TCP Reset-O&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:57 ASA : %ASA-6-302013: Built outbound TCP connection 173523129 for outside:2.2.2.2/8585 (2.2.2.2/8585) to inside:10.249.102.230/52781 (10.249.102.230/52781)&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:58 ASA : %ASA-6-302013: Built outbound TCP connection 173523287 for outside:3.3.3.3/80 (3.3.3.3/80) to inside:10.249.102.230/53036 (10.249.102.230/53036)&lt;/P&gt;&lt;P&gt;Feb 17 2013 12:45:59 ASA : %ASA-6-302014: Teardown TCP connection 173523287 for outside:3.3.3.3/80 to inside:10.249.102.230/53036 duration 0:00:00 bytes 110 TCP Reset-O&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:01:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185958#M361869</guid>
      <dc:creator>n3tw0rkguy83</dc:creator>
      <dc:date>2019-03-12T01:01:49Z</dc:date>
    </item>
    <item>
      <title>Interpretting Logs on the Firewall</title>
      <link>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185959#M361871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What do you see when running the "netstat -a" line on your PC?&lt;/P&gt;&lt;P&gt;Do you get to the same website when typing both addresses in your browser's navigation bar?&lt;/P&gt;&lt;P&gt;Are the users we are talking about using the same DNS server and path to access this webserver?&lt;/P&gt;&lt;P&gt;What do you think the ASA is doing with the DNS/HTTP traffic?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 03:09:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185959#M361871</guid>
      <dc:creator>jocamare</dc:creator>
      <dc:date>2013-02-19T03:09:07Z</dc:date>
    </item>
    <item>
      <title>Interpretting Logs on the Firewall</title>
      <link>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185960#M361872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sorry, clicked on "correct answer". I dont' really know how these tagging of correct answers or useful answer works...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What do you see when running the "netstat -a" line on your PC?&lt;/P&gt;&lt;P&gt;-anyway, regarding netstat, i wasn't able to capture that when the issue occured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you get to the same website when typing both addresses in your browser's navigation bar?&lt;/P&gt;&lt;P&gt;-typing 3.3.3.3, shows an error. but when i typed 2.2.2.2, it accesses the correct website.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are the users we are talking about using the same DNS server and path to access this webserver?&lt;/P&gt;&lt;P&gt;-they have their internal dns server, and have a forward lookup zone to access 2.2.2.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What do you think the ASA is doing with the DNS/HTTP traffic?&lt;/P&gt;&lt;P&gt;-i think the ASA is just letting the traffic pass through. we're not blocking anything going to those addresses.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Feb 2013 15:32:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185960#M361872</guid>
      <dc:creator>n3tw0rkguy83</dc:creator>
      <dc:date>2013-02-20T15:32:05Z</dc:date>
    </item>
    <item>
      <title>Interpretting Logs on the Firewall</title>
      <link>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185961#M361873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since there is only one site reporting a dfferent behavior, i would assume that this address [3.3.3.3] is being translated to the ip everybody is seeing [2.2.2.2].&amp;nbsp; Can you share the configuration of the ASA?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What happens if you configure a different DNS server for the clients that are using the client's DNS server?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Feb 2013 17:29:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185961#M361873</guid>
      <dc:creator>jocamare</dc:creator>
      <dc:date>2013-02-20T17:29:47Z</dc:date>
    </item>
    <item>
      <title>Interpretting Logs on the Firewall</title>
      <link>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185962#M361874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i apologize, it's not possible. this is a client facing ASA. &lt;SPAN __jive_emoticon_name="sad" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/sad.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What happens if you configure a different DNS server for the clients that are using the client's DNS server?&lt;/P&gt;&lt;P&gt;&amp;nbsp; -haven't tried this though. what's weird is that we compared nslookup results with the other IT personel from the other site and used the same dns server, but shows different results.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Feb 2013 17:12:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185962#M361874</guid>
      <dc:creator>n3tw0rkguy83</dc:creator>
      <dc:date>2013-02-22T17:12:28Z</dc:date>
    </item>
    <item>
      <title>Interpretting Logs on the Firewall</title>
      <link>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185963#M361875</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The ASA might be modifying the DNS reply if its configured to do so, check for the "dns" keyword at the end of the static translations. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Feb 2013 18:15:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185963#M361875</guid>
      <dc:creator>jocamare</dc:creator>
      <dc:date>2013-02-22T18:15:25Z</dc:date>
    </item>
    <item>
      <title>Interpretting Logs on the Firewall</title>
      <link>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185964#M361876</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i will do so. thanks for your help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2013 15:59:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/interpretting-logs-on-the-firewall/m-p/2185964#M361876</guid>
      <dc:creator>n3tw0rkguy83</dc:creator>
      <dc:date>2013-02-27T15:59:42Z</dc:date>
    </item>
  </channel>
</rss>

