<?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 ASA dns in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-dns/m-p/4685970#M1093336</link>
    <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.png" style="width: 715px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/162322i58FF1110BC2F1332/image-size/large?v=v2&amp;amp;px=999" role="button" title="1.png" alt="1.png" /&gt;&lt;/span&gt;&lt;FONT&gt;如图，在局域网内是没有DNS的，客户端是通过ASA dhcp下发的外部DNS地址。内部网络中有一台服务器，和客户端是在同一个局域网中，现在的要求是Client可以通过计算机名（或域名）&lt;SPAN&gt;demo.mydomain.com 访问www server，应该如何配置ASA？Client数据太多，编辑host文件的方法不适用。&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 13 Sep 2022 08:10:49 GMT</pubDate>
    <dc:creator>332953358</dc:creator>
    <dc:date>2022-09-13T08:10:49Z</dc:date>
    <item>
      <title>ASA dns</title>
      <link>https://community.cisco.com/t5/network-security/asa-dns/m-p/4685970#M1093336</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.png" style="width: 715px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/162322i58FF1110BC2F1332/image-size/large?v=v2&amp;amp;px=999" role="button" title="1.png" alt="1.png" /&gt;&lt;/span&gt;&lt;FONT&gt;如图，在局域网内是没有DNS的，客户端是通过ASA dhcp下发的外部DNS地址。内部网络中有一台服务器，和客户端是在同一个局域网中，现在的要求是Client可以通过计算机名（或域名）&lt;SPAN&gt;demo.mydomain.com 访问www server，应该如何配置ASA？Client数据太多，编辑host文件的方法不适用。&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2022 08:10:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dns/m-p/4685970#M1093336</guid>
      <dc:creator>332953358</dc:creator>
      <dc:date>2022-09-13T08:10:49Z</dc:date>
    </item>
    <item>
      <title>Re: ASA dns</title>
      <link>https://community.cisco.com/t5/network-security/asa-dns/m-p/4685978#M1093338</link>
      <description>&lt;P&gt;重要的一点是 www server 不能发布到internet上&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2022 08:24:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dns/m-p/4685978#M1093338</guid>
      <dc:creator>332953358</dc:creator>
      <dc:date>2022-09-13T08:24:27Z</dc:date>
    </item>
    <item>
      <title>Re: ASA dns</title>
      <link>https://community.cisco.com/t5/network-security/asa-dns/m-p/4685985#M1093341</link>
      <description>&lt;P&gt;Hey.&lt;/P&gt;
&lt;P&gt;Have a look on these link cisco already showed the configuration of this setup&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/72273-dns-doctoring-3zones.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/72273-dns-doctoring-3zones.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/115753-dns-doctoring-asa-config.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/115753-dns-doctoring-asa-config.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2022 08:37:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dns/m-p/4685985#M1093341</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2022-09-13T08:37:52Z</dc:date>
    </item>
    <item>
      <title>Re: ASA dns</title>
      <link>https://community.cisco.com/t5/network-security/asa-dns/m-p/4685992#M1093342</link>
      <description>&lt;P&gt;Depends on if you want the server to gets back to the client with its public or private IP address you can apply one of the following solutions:&lt;/P&gt;
&lt;P&gt;To be able to reach the internal server with its public IP and get the replies sourcing from the server's public IP:&lt;/P&gt;
&lt;P&gt;nat (inside,inside) source dynamic &amp;lt; LAN subnet object &amp;gt; interface destination static &amp;lt; Server public IP object &amp;gt; &amp;lt; Server private IP object &amp;gt;&lt;BR /&gt;nat (inside,outside) source static &amp;lt; Server private IP object &amp;gt; &amp;lt; Server public IP object &amp;gt;&lt;BR /&gt;nat (inside,outside) after-auto source dynamic &amp;lt; LAN subnet object &amp;gt; interface&lt;/P&gt;
&lt;P&gt;To be able to reach the internal server with its public IP and get the replies sourcing from the server's private IP:&lt;/P&gt;
&lt;P&gt;nat (inside,any) source static &amp;lt; Server private IP object &amp;gt; &amp;lt; Server public IP object &amp;gt;&lt;BR /&gt;nat (inside,outside) source dynamic &amp;lt; LAN subnet object &amp;gt; interface&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2022 08:55:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dns/m-p/4685992#M1093342</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2022-09-13T08:55:39Z</dc:date>
    </item>
  </channel>
</rss>

