<?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 Nat question. faking dynamic, but only allow incoming to 1 host in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-question-faking-dynamic-but-only-allow-incoming-to-1-host/m-p/1488575#M701459</link>
    <description>&lt;P&gt;I have 1 external IP address that is used for incomming mail.&amp;nbsp; That address is pointed via static to my Barracuda web filter.&amp;nbsp; My xchange server falls under the standard dynamic nat policy.&amp;nbsp; One some domains I have been getting NDR bounce backs because the source IP address does not mach my MX record address (reverse dns).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IE..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;123.123.123.123 is the external IP address for my internal host 172.16.1.1&amp;nbsp; (my barracuda)&lt;/P&gt;&lt;P&gt;123.123.123.223 is the external IP address for my internal dynamic nat.&amp;nbsp; (so all other hosts appear under this address, which includes my exchage server).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to mask / fake so that my exchange server appears to have the same external address as my barracuda to prevent these NDR reverse dns issues?&amp;nbsp; However I do not want anything that goes to 123.123.123.123 to go directly to the exchange server.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 17:41:11 GMT</pubDate>
    <dc:creator>ksuchewie</dc:creator>
    <dc:date>2019-03-11T17:41:11Z</dc:date>
    <item>
      <title>Nat question. faking dynamic, but only allow incoming to 1 host</title>
      <link>https://community.cisco.com/t5/network-security/nat-question-faking-dynamic-but-only-allow-incoming-to-1-host/m-p/1488575#M701459</link>
      <description>&lt;P&gt;I have 1 external IP address that is used for incomming mail.&amp;nbsp; That address is pointed via static to my Barracuda web filter.&amp;nbsp; My xchange server falls under the standard dynamic nat policy.&amp;nbsp; One some domains I have been getting NDR bounce backs because the source IP address does not mach my MX record address (reverse dns).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IE..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;123.123.123.123 is the external IP address for my internal host 172.16.1.1&amp;nbsp; (my barracuda)&lt;/P&gt;&lt;P&gt;123.123.123.223 is the external IP address for my internal dynamic nat.&amp;nbsp; (so all other hosts appear under this address, which includes my exchage server).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to mask / fake so that my exchange server appears to have the same external address as my barracuda to prevent these NDR reverse dns issues?&amp;nbsp; However I do not want anything that goes to 123.123.123.123 to go directly to the exchange server.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:41:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-question-faking-dynamic-but-only-allow-incoming-to-1-host/m-p/1488575#M701459</guid>
      <dc:creator>ksuchewie</dc:creator>
      <dc:date>2019-03-11T17:41:11Z</dc:date>
    </item>
    <item>
      <title>Re: Nat question. faking dynamic, but only allow incoming to 1 h</title>
      <link>https://community.cisco.com/t5/network-security/nat-question-faking-dynamic-but-only-allow-incoming-to-1-host/m-p/1488576#M701470</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume that we have the following configuration:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 123.123.123.123 172.16.1.1&lt;/P&gt;&lt;P&gt;global (outside) 1 123.123.123.223&lt;/P&gt;&lt;P&gt;nat (inside) 1 0 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no static (inside,outside) 123.123.123.123 172.16.1.1&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp 123.123.123.123 25 172.16.1.1 25&lt;/P&gt;&lt;P&gt;no global (outside) 1 123.123.123.223&lt;/P&gt;&lt;P&gt;global (outside) 1 123.123.123.123&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;clear xlate&lt;/P&gt;&lt;P&gt;clear local&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if that resolves the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ashu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 May 2010 14:02:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-question-faking-dynamic-but-only-allow-incoming-to-1-host/m-p/1488576#M701470</guid>
      <dc:creator>astripat</dc:creator>
      <dc:date>2010-05-05T14:02:55Z</dc:date>
    </item>
    <item>
      <title>Re: Nat question. faking dynamic, but only allow incoming to 1 h</title>
      <link>https://community.cisco.com/t5/network-security/nat-question-faking-dynamic-but-only-allow-incoming-to-1-host/m-p/1488577#M701481</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should not do that as if the exchange server gets hit with a virus or mass mailing bot you will get on the SPAM list and could have issues with the server.&amp;nbsp; You should point your exchange server at the Barracuda as an SMTP smarthost and have it scan outbound.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 May 2010 03:13:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-question-faking-dynamic-but-only-allow-incoming-to-1-host/m-p/1488577#M701481</guid>
      <dc:creator>bob.bartlett</dc:creator>
      <dc:date>2010-05-06T03:13:37Z</dc:date>
    </item>
  </channel>
</rss>

