<?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: PIX/NAT/Dynamic DNS in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-nat-dynamic-dns/m-p/584495#M502239</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I din't think it is possible to have client machines inside a PIX sending dynamic dns updates to an AD/DNS server outside the firewall when using NAT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Apr 2006 15:02:06 GMT</pubDate>
    <dc:creator>sbilgi</dc:creator>
    <dc:date>2006-04-26T15:02:06Z</dc:date>
    <item>
      <title>PIX/NAT/Dynamic DNS</title>
      <link>https://community.cisco.com/t5/network-security/pix-nat-dynamic-dns/m-p/584494#M502238</link>
      <description>&lt;P&gt;Is it possible to have client machines inside a PIX sending dynamic dns updates to an AD/DNS server outside the firewall when using NAT?  If so, is this supposed to be handled by the normal dns fixup/inspection, or does something have to be specifically configured?  Is there any version restriction on the solution (if any)?  Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:50:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-nat-dynamic-dns/m-p/584494#M502238</guid>
      <dc:creator>lowen</dc:creator>
      <dc:date>2020-02-21T08:50:57Z</dc:date>
    </item>
    <item>
      <title>Re: PIX/NAT/Dynamic DNS</title>
      <link>https://community.cisco.com/t5/network-security/pix-nat-dynamic-dns/m-p/584495#M502239</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I din't think it is possible to have client machines inside a PIX sending dynamic dns updates to an AD/DNS server outside the firewall when using NAT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Apr 2006 15:02:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-nat-dynamic-dns/m-p/584495#M502239</guid>
      <dc:creator>sbilgi</dc:creator>
      <dc:date>2006-04-26T15:02:06Z</dc:date>
    </item>
    <item>
      <title>Re: PIX/NAT/Dynamic DNS</title>
      <link>https://community.cisco.com/t5/network-security/pix-nat-dynamic-dns/m-p/584496#M502240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you have another firewall between the AD/DNS servers and the Internet? If not you could be in for a rude awakening someday!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't see the purpose of doing dynamic updates to DNS via NAT, when the address' for the hosts won't be the same for any length of time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is always best to separate DNS for internal zones and public zones, otherwise someone with malicious intent will be able to find out the names of your internal hosts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know that there are reasons to run both internal and external dns on the same server, but I don't see this in your case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This may not be the answer that you are looking for, but hopefully it will be worth something to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;G'Day,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Roger&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Apr 2006 21:41:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-nat-dynamic-dns/m-p/584496#M502240</guid>
      <dc:creator>genghiskhan</dc:creator>
      <dc:date>2006-04-26T21:41:21Z</dc:date>
    </item>
  </channel>
</rss>

