<?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 Having internal hosts access DMZ hosts with external DNS name but private IP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/having-internal-hosts-access-dmz-hosts-with-external-dns-name/m-p/1797695#M533747</link>
    <description>&lt;P&gt;Three interface ASA Scenario: Inside 10.10.10.0/24&amp;nbsp;&amp;nbsp;&amp;nbsp; Outside 4.4.4.10/24&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DMZ 192.168.1.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;External users resolve &lt;A href="https://community.cisco.com/www.acme.com" target="_blank"&gt;www.acme.com&lt;/A&gt; to 4.4.4.10 say.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want internal users to resolve using external DNS but when they that traffic gets&lt;/P&gt;&lt;P&gt;to the ASA I want the traffic to go to 192.168.1.10 the private IP of the server instead&lt;/P&gt;&lt;P&gt;of trying to go outside and failing.&amp;nbsp; I don't want to have a different internal DNS&lt;/P&gt;&lt;P&gt;setup for a bunch of reasons.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the best current method to do this?&amp;nbsp; I am running ASA OS 8.2.&amp;nbsp; &lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 21:10:32 GMT</pubDate>
    <dc:creator>mmedwid</dc:creator>
    <dc:date>2019-03-11T21:10:32Z</dc:date>
    <item>
      <title>Having internal hosts access DMZ hosts with external DNS name but private IP</title>
      <link>https://community.cisco.com/t5/network-security/having-internal-hosts-access-dmz-hosts-with-external-dns-name/m-p/1797695#M533747</link>
      <description>&lt;P&gt;Three interface ASA Scenario: Inside 10.10.10.0/24&amp;nbsp;&amp;nbsp;&amp;nbsp; Outside 4.4.4.10/24&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DMZ 192.168.1.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;External users resolve &lt;A href="https://community.cisco.com/www.acme.com" target="_blank"&gt;www.acme.com&lt;/A&gt; to 4.4.4.10 say.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want internal users to resolve using external DNS but when they that traffic gets&lt;/P&gt;&lt;P&gt;to the ASA I want the traffic to go to 192.168.1.10 the private IP of the server instead&lt;/P&gt;&lt;P&gt;of trying to go outside and failing.&amp;nbsp; I don't want to have a different internal DNS&lt;/P&gt;&lt;P&gt;setup for a bunch of reasons.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the best current method to do this?&amp;nbsp; I am running ASA OS 8.2.&amp;nbsp; &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:10:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/having-internal-hosts-access-dmz-hosts-with-external-dns-name/m-p/1797695#M533747</guid>
      <dc:creator>mmedwid</dc:creator>
      <dc:date>2019-03-11T21:10:32Z</dc:date>
    </item>
    <item>
      <title>Having internal hosts access DMZ hosts with external DNS name bu</title>
      <link>https://community.cisco.com/t5/network-security/having-internal-hosts-access-dmz-hosts-with-external-dns-name/m-p/1797696#M533749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;DNS doctoring is the way to do this. See this document for details on how to configure this - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807968c8.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807968c8.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Aug 2011 22:17:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/having-internal-hosts-access-dmz-hosts-with-external-dns-name/m-p/1797696#M533749</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2011-08-11T22:17:13Z</dc:date>
    </item>
  </channel>
</rss>

