<?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 Firewall &amp; DNS Records in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418738#M306728</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this is what i use to do each time&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 30 Dec 2013 17:33:36 GMT</pubDate>
    <dc:creator>Ahmad Khalifa</dc:creator>
    <dc:date>2013-12-30T17:33:36Z</dc:date>
    <item>
      <title>Firewall &amp; DNS Records</title>
      <link>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418732#M306706</link>
      <description>&lt;P&gt;I have this Senario as in attatchemnt &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; i have WEB Server into the Inside Network is NAT to Outside &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; when a client in the Outside Trying to Use the Resolved IP from the DNS the DNS reply by the IP that on the Inside for the Server itself before NAT&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Any Idea to prevent the ASA5510 to Send the Inside IP tp the Outside DNS???&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 03:21:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418732#M306706</guid>
      <dc:creator>Ahmad Khalifa</dc:creator>
      <dc:date>2019-03-12T03:21:49Z</dc:date>
    </item>
    <item>
      <title>Firewall &amp; DNS Records</title>
      <link>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418733#M306709</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ahmad,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have static NAT translating outside IP to the inside one ASA will not send inside IP to the outside DNS.&lt;/P&gt;&lt;P&gt;But this is not very clear and I am not sure if I properly understood your post, so can you include your NAT config please?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mariusz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Dec 2013 11:46:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418733#M306709</guid>
      <dc:creator>Mariusz Bochen</dc:creator>
      <dc:date>2013-12-27T11:46:17Z</dc:date>
    </item>
    <item>
      <title>Firewall &amp; DNS Records</title>
      <link>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418734#M306712</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no communication between the ASA and the DNS-server. So the ASA doesn't send anthing to the DNS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding to your diagram, the DNS-server has a mapping to the internal address. A public DNS should always be configured with the public IP which would be 192.168.100.200 in your case. With that, the outside client would resolve the name to the right IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;nbsp; &lt;BR /&gt;Don't stop after you've improved your network! Improve the world by lending money to the working poor: &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.kiva.org/invitedby/karsteni"&gt;http://www.kiva.org/invitedby/karsteni&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Dec 2013 12:34:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418734#M306712</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2013-12-27T12:34:19Z</dc:date>
    </item>
    <item>
      <title>Firewall &amp; DNS Records</title>
      <link>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418735#M306716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; thank you for your Concern &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; when i run NSLOOKUP from the Client on the OutSide with the name of the WEB Server its Reply by the Internal IP Before NAT (LOCAL IP)&lt;/P&gt;&lt;P&gt;its Happen With me in 2 Different Sites &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Dec 2013 12:43:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418735#M306716</guid>
      <dc:creator>Ahmad Khalifa</dc:creator>
      <dc:date>2013-12-27T12:43:38Z</dc:date>
    </item>
    <item>
      <title>Firewall &amp; DNS Records</title>
      <link>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418736#M306721</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;but its happen when you run cmd "nslookup" its reply by intenal IP noth the Global IP any idea&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Dec 2013 16:54:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418736#M306721</guid>
      <dc:creator>Ahmad Khalifa</dc:creator>
      <dc:date>2013-12-30T16:54:20Z</dc:date>
    </item>
    <item>
      <title>Firewall &amp; DNS Records</title>
      <link>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418737#M306725</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have to correct that on the DNS-server. There the public IP should be configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;nbsp; &lt;BR /&gt;Don't stop after you've improved your network! Improve the world by lending money to the working poor: &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.kiva.org/invitedby/karsteni"&gt;http://www.kiva.org/invitedby/karsteni&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Dec 2013 17:03:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418737#M306725</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2013-12-30T17:03:40Z</dc:date>
    </item>
    <item>
      <title>Firewall &amp; DNS Records</title>
      <link>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418738#M306728</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this is what i use to do each time&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Dec 2013 17:33:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418738#M306728</guid>
      <dc:creator>Ahmad Khalifa</dc:creator>
      <dc:date>2013-12-30T17:33:36Z</dc:date>
    </item>
    <item>
      <title>Firewall &amp; DNS Records</title>
      <link>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418739#M306730</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What do you mean with "each time"? Is your change not permanent? What kind of DNS-server is it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;nbsp; &lt;BR /&gt;Don't stop after you've improved your network! Improve the world by lending money to the working poor: &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.kiva.org/invitedby/karsteni"&gt;http://www.kiva.org/invitedby/karsteni&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Dec 2013 18:13:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-dns-records/m-p/2418739#M306730</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2013-12-30T18:13:48Z</dc:date>
    </item>
  </channel>
</rss>

