<?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 PIX and internal DNS Server in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-and-internal-dns-server/m-p/308263#M561281</link>
    <description>&lt;P&gt;I currently have two internal Win2K3 DNS servers on my internal network that had been working fine.  I tried to upgrade my PIX os from 5.1.2 to 6.3.x but that stopped all traffic. I downgraded to 5.2.9 which allowed at least email to flow in again.  The problem is that my internal DNS servers now cannot resolve requests from the outside.  If I put in the IP of my IPS' DNS servers on the client, it works.  The config has not changed but still does not work.  Please help this rookie.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 07:36:30 GMT</pubDate>
    <dc:creator>rgonzaga</dc:creator>
    <dc:date>2020-02-21T07:36:30Z</dc:date>
    <item>
      <title>PIX and internal DNS Server</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-internal-dns-server/m-p/308263#M561281</link>
      <description>&lt;P&gt;I currently have two internal Win2K3 DNS servers on my internal network that had been working fine.  I tried to upgrade my PIX os from 5.1.2 to 6.3.x but that stopped all traffic. I downgraded to 5.2.9 which allowed at least email to flow in again.  The problem is that my internal DNS servers now cannot resolve requests from the outside.  If I put in the IP of my IPS' DNS servers on the client, it works.  The config has not changed but still does not work.  Please help this rookie.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:36:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-internal-dns-server/m-p/308263#M561281</guid>
      <dc:creator>rgonzaga</dc:creator>
      <dc:date>2020-02-21T07:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: PIX and internal DNS Server</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-internal-dns-server/m-p/308264#M561282</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This should be fixed with 6.3.3 and higher be sure that you have the:&lt;/P&gt;&lt;P&gt;" fixup protocol dns maximum-length 512 "&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this does not works try:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Workarround two use the alias command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See:&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a0080094aee.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a0080094aee.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;alias (inside) 10.10.10.10 99.99.99.99 255.255.255.255&lt;/P&gt;&lt;P&gt;!--- This command sets up DNS Doctoring. It is initiated from the clients in&lt;/P&gt;&lt;P&gt;!--- the "inside" network. It watches for DNS replies that contain&lt;/P&gt;&lt;P&gt;!--- 99.99.99.99, then replaces the 99.99.99.99 address with the 10.10.10.10&lt;/P&gt;&lt;P&gt;!--- address in the "DNS reply" sent to the client PC. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sincerly&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Sep 2004 15:29:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-internal-dns-server/m-p/308264#M561282</guid>
      <dc:creator>piseli</dc:creator>
      <dc:date>2004-09-03T15:29:59Z</dc:date>
    </item>
  </channel>
</rss>

