<?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 NAT in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681339#M191626</link>
    <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; I would like to know the procedure or any documents how to create a&amp;nbsp;nat rule for DNS.And also explain me what is DNS nat and which sceanrio we need to implement the DNS nat.&lt;/P&gt;&lt;P&gt;Please confirm the DNS nat and DNS ALG are same?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:55:45 GMT</pubDate>
    <dc:creator>dhinesh_83</dc:creator>
    <dc:date>2019-03-12T05:55:45Z</dc:date>
    <item>
      <title>DNS NAT</title>
      <link>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681339#M191626</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; I would like to know the procedure or any documents how to create a&amp;nbsp;nat rule for DNS.And also explain me what is DNS nat and which sceanrio we need to implement the DNS nat.&lt;/P&gt;&lt;P&gt;Please confirm the DNS nat and DNS ALG are same?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:55:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681339#M191626</guid>
      <dc:creator>dhinesh_83</dc:creator>
      <dc:date>2019-03-12T05:55:45Z</dc:date>
    </item>
    <item>
      <title>This is probably what you are</title>
      <link>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681340#M191627</link>
      <description>&lt;P&gt;This is probably what you are looking for if you are interested in the ASA:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/115753-dns-doctoring-asa-config.html"&gt;http://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;DNS NAT is a function that could be implemented on a DNS ALG, but they are not automatically the same.&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2015 13:31:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681340#M191627</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-05-13T13:31:23Z</dc:date>
    </item>
    <item>
      <title>Thank you very much for the</title>
      <link>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681341#M191629</link>
      <description>&lt;P&gt;Thank you very much for the update.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you have any procedure/Document&amp;nbsp;how to implement the DNS NAT in cisco router.&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2015 12:27:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681341#M191629</guid>
      <dc:creator>dhinesh_83</dc:creator>
      <dc:date>2015-05-14T12:27:11Z</dc:date>
    </item>
    <item>
      <title>Hi Karsten,       Please</title>
      <link>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681342#M191631</link>
      <description>&lt;P&gt;Hi Karsten,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; Please share me any sample configuration for DNS NAT in Cisco.&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2015 11:14:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681342#M191631</guid>
      <dc:creator>dhinesh_83</dc:creator>
      <dc:date>2015-05-18T11:14:24Z</dc:date>
    </item>
    <item>
      <title>A config sample is in the</title>
      <link>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681343#M191632</link>
      <description>&lt;P&gt;A config sample is in the above link.&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2015 11:19:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681343#M191632</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-05-18T11:19:34Z</dc:date>
    </item>
    <item>
      <title>Thanks for the update.Can you</title>
      <link>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681344#M191633</link>
      <description>&lt;P&gt;Thanks for the update.Can you please help me the configuration for the below setup&lt;/P&gt;&lt;P&gt;Please find the attached setup for your reference.&lt;/P&gt;&lt;P&gt;When user in &amp;nbsp;A network tries to access one of the server(abc.com) in B network via hostname.The packet first hit the&amp;nbsp;A N/W&amp;nbsp;DNS for requsting the abc.com ip address.Again they will forward the requset to B N/W DNS for the ip address.They retrun back the ip address say example(10.1.1.5) for respective hostname.But we have the 10.1.1.0/24 already using in A N/W.In that case we need to do the nat in the firewall. How we implement the DNS NAT in the Cisco ASA firewall.&lt;/P&gt;&lt;P&gt;Can you please share the configuration how to implement this setup.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2015 12:55:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681344#M191633</guid>
      <dc:creator>dhinesh_83</dc:creator>
      <dc:date>2015-05-18T12:55:46Z</dc:date>
    </item>
    <item>
      <title>It's a homework, isn't it</title>
      <link>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681345#M191634</link>
      <description>&lt;P&gt;It's a homework, isn't it?&lt;/P&gt;&lt;P&gt;There are multiple problems in that task:&lt;/P&gt;&lt;P&gt;1) Translating DNS-replys is not enough. You also need to translate the 10.1.1.0 network in both directions (Double-NAT).&lt;/P&gt;&lt;P&gt;2) The next part is that DNS-replies need to resolve to a different address. This is exactly an scenario in the referenced link which doesn't work easily on the ASA. For that, DNS-views can be configured on the DNS-server. With DNS-views, the server returns different A-records based on the source-IP of the query.&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2015 13:40:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681345#M191634</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-05-18T13:40:05Z</dc:date>
    </item>
    <item>
      <title>Thanks for the inputs karsten</title>
      <link>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681346#M191635</link>
      <description>&lt;P&gt;Thanks for the inputs karsten.&lt;/P&gt;&lt;P&gt;I understand the first step you mentioned we need to do the NAT in both directions.&lt;/P&gt;&lt;P&gt;Second step is very hard to understand to proceed.Reference link which you gave also not clear to do the config.&lt;/P&gt;&lt;P&gt;I will prepare the config and share you the same to you.Please review.&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2015 16:36:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681346#M191635</guid>
      <dc:creator>dhinesh_83</dc:creator>
      <dc:date>2015-05-18T16:36:32Z</dc:date>
    </item>
    <item>
      <title>Please find below the config</title>
      <link>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681347#M191636</link>
      <description>&lt;P&gt;Please find below the config for your review.Please correct me if am wrong.The DNS NAT config is highlighted.My requirement is when user is access the server via hostname 192.168.1.5(abc.com) it should be natted to 10.10.20.5.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;hostname ASA1&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0&lt;BR /&gt;&amp;nbsp;nameif outside&lt;BR /&gt;&amp;nbsp;security-level 0&lt;BR /&gt;&amp;nbsp;ip address y.y.y.y 255.255.255.252&lt;BR /&gt;&amp;nbsp;no shut&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1&lt;BR /&gt;&amp;nbsp;nameif inside&lt;BR /&gt;&amp;nbsp;security-level 100&lt;BR /&gt;&amp;nbsp;ip address 192.168.1.1 255.255.255.0&lt;BR /&gt;&amp;nbsp;no shut&lt;BR /&gt;!&lt;BR /&gt;object network inside-mapped-network&lt;BR /&gt;&amp;nbsp;subnet 10.10.10.0 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;object network inside-real-network&lt;BR /&gt;&amp;nbsp;subnet 192.168.1.0 255.255.255.0&lt;BR /&gt;&amp;nbsp;nat (inside,outside) static inside-mapped-network&lt;BR /&gt;!&lt;BR /&gt;access-list CRYPTO_ACL extended permit ip 10.10.10.0 255.255.255.0 10.10.20.0 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;route outside 10.10.20.0 255.255.255.0 Y.Y.Y.Y&lt;BR /&gt;!&lt;BR /&gt;crypto ipsec ikev1 transform-set TRANS_SET esp-3des esp-md5-hmac&lt;BR /&gt;crypto map CRYP_MAP 10 match address CRYPTO_ACL&lt;BR /&gt;crypto map CRYP_MAP 10 set peer 41.1.1.2&lt;BR /&gt;crypto map CRYP_MAP 10 set ikev1 transform-set TRANS_SET&lt;BR /&gt;crypto map CRYP_MAP interface outside&lt;BR /&gt;crypto ikev1 enable outside&lt;BR /&gt;crypto ikev1 policy 1&lt;BR /&gt;&amp;nbsp;authentication pre-share&lt;BR /&gt;&amp;nbsp;encryption 3des&lt;BR /&gt;&amp;nbsp;hash sha&lt;BR /&gt;&amp;nbsp;group 2&lt;BR /&gt;&amp;nbsp;lifetime 86400&lt;BR /&gt;!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;hostname ASA2&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0&lt;BR /&gt;&amp;nbsp;nameif outside&lt;BR /&gt;&amp;nbsp;security-level 0&lt;BR /&gt;&amp;nbsp;ip address Y.Y.Y.Y 255.255.255.252&lt;BR /&gt;&amp;nbsp;no shut&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1&lt;BR /&gt;&amp;nbsp;nameif inside&lt;BR /&gt;&amp;nbsp;security-level 100&lt;BR /&gt;&amp;nbsp;ip address 192.168.1.1 255.255.255.0&lt;BR /&gt;&amp;nbsp;no shut&lt;BR /&gt;!&lt;BR /&gt;object network inside-mapped-network&lt;BR /&gt;&amp;nbsp;subnet 10.10.20.0 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;object network inside-real-network&lt;BR /&gt;&amp;nbsp;subnet 192.168.1.0 255.255.255.0&lt;BR /&gt;&amp;nbsp;nat (inside,outside) static inside-mapped-network&lt;BR /&gt;!&lt;BR /&gt;&lt;STRONG&gt;&amp;nbsp;nat (inside,outside) source static 192.168.1.5 10.10.20.5 dns&lt;BR /&gt;!&lt;BR /&gt;policy-map global_policy&lt;BR /&gt;&amp;nbsp; class inspection_default&amp;nbsp;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; inspect dns&lt;/STRONG&gt;&lt;BR /&gt;!&lt;BR /&gt;access-list CRYPTO_ACL extended permit ip 10.10.20.0 255.255.255.0 10.10.10.0 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;route outside 10.10.10.0 255.255.255.0 Y.Y.Y.Y&lt;BR /&gt;!&lt;BR /&gt;crypto ipsec ikev1 transform-set TRANS_SET esp-3des esp-md5-hmac&lt;BR /&gt;crypto map CRYP_MAP 10 match address CRYPTO_ACL&lt;BR /&gt;crypto map CRYP_MAP 10 set peer Y.Y.Y.Y&lt;BR /&gt;crypto map CRYP_MAP 10 set ikev1 transform-set TRANS_SET&lt;BR /&gt;crypto map CRYP_MAP interface outside&lt;BR /&gt;crypto ikev1 enable outside&lt;BR /&gt;crypto ikev1 policy 1&lt;BR /&gt;&amp;nbsp;authentication pre-share&lt;BR /&gt;&amp;nbsp;encryption 3des&lt;BR /&gt;&amp;nbsp;hash sha&lt;BR /&gt;&amp;nbsp;group 2&lt;BR /&gt;&amp;nbsp;lifetime 86400&lt;BR /&gt;!&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2015 17:29:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dns-nat/m-p/2681347#M191636</guid>
      <dc:creator>dhinesh_83</dc:creator>
      <dc:date>2015-05-18T17:29:00Z</dc:date>
    </item>
  </channel>
</rss>

