<?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 Re: Reverse DNS Issue with Barracuda Spam Filter in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/reverse-dns-issue-with-barracuda-spam-filter/m-p/1137284#M894640</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Chris,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a reverse static route for the Barracuda. currently sounds like you are using a global NAT for all Inside IP address, try the below:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (outside,inside) 10.0.0.6 1.2.3.5 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Oct 2008 11:31:59 GMT</pubDate>
    <dc:creator>andrew.prince</dc:creator>
    <dc:date>2008-10-23T11:31:59Z</dc:date>
    <item>
      <title>Reverse DNS Issue with Barracuda Spam Filter</title>
      <link>https://community.cisco.com/t5/network-security/reverse-dns-issue-with-barracuda-spam-filter/m-p/1137283#M894639</link>
      <description>&lt;P&gt;Hi, I have a Barracuda Spam Filter which accepts our incoming smtp and passes it on to our Exchange Server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For Outgoing emails the Exchange server sends directly out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have static Nats set up as follows (external IP's replaced)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exchange Server&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (INSIDE,OUTSIDE) 1.2.3.4 10.0.0.5 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Barracuda&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (INSIDE,OUTSIDE) 1.2.3.5 10.0.0.6 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;also access-lists as follows&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exchange (https &amp;amp; www for Outlook Web Access)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list OUTSIDEIN extended permit tcp any host 1.2.3.4 eq https&lt;/P&gt;&lt;P&gt;access-list OUTSIDEIN extended permit tcp any host 1.2.3.4 eq www&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Barracuda (incoming SMTP)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list OUTSIDEIN extended permit tcp any host 1.2.3.5 eq smtp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problem is when I send emails out, it goes out as 1.2.3.4 which does not match up with the MX record that points to 1.2.3.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore we are receiving Reverse DNS failures from recipients&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;exchange1.ourdomain.local #5.7.1 smtp;550 5.7.1 Client host rejected: cannot find your hostname, [1.2.3.4]&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible for our Exchange Server to send out via 1.2.3.5 ? (I cannot use the Barracuda as an outgoing relay)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 14:01:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/reverse-dns-issue-with-barracuda-spam-filter/m-p/1137283#M894639</guid>
      <dc:creator>shaw.chris</dc:creator>
      <dc:date>2019-03-11T14:01:46Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse DNS Issue with Barracuda Spam Filter</title>
      <link>https://community.cisco.com/t5/network-security/reverse-dns-issue-with-barracuda-spam-filter/m-p/1137284#M894640</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Chris,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a reverse static route for the Barracuda. currently sounds like you are using a global NAT for all Inside IP address, try the below:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (outside,inside) 10.0.0.6 1.2.3.5 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Oct 2008 11:31:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/reverse-dns-issue-with-barracuda-spam-filter/m-p/1137284#M894640</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2008-10-23T11:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse DNS Issue with Barracuda Spam Filter</title>
      <link>https://community.cisco.com/t5/network-security/reverse-dns-issue-with-barracuda-spam-filter/m-p/1137285#M894641</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Andrew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would I need this static NAT for the Exchange Server (10.0.0.5) rather than the Barracuda as I want the Exchange server to go out as 1.2.3.5?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do have Global Nat set up using the Interface address for all inside hosts, but neither the Barracuda or Exchange Server use that address, they currently go out using the addresses I have set up in the Static NATs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Oct 2008 11:41:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/reverse-dns-issue-with-barracuda-spam-filter/m-p/1137285#M894641</guid>
      <dc:creator>shaw.chris</dc:creator>
      <dc:date>2008-10-23T11:41:55Z</dc:date>
    </item>
  </channel>
</rss>

