<?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 blocks Windows Server 2003 EDNS0(DNS) replies. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402244#M558780</link>
    <description>&lt;P&gt;PIX Firewall earlier than version 6.3(2) block dns query responses if query comes from Server 2003 and the external DNS server supports EDNSO.  Microsoft's workaround of disabling DNS-Probes did not solve the problem.  Short of updating the IOS is there a way to change the DNS-UDP packet size limit that is currently set on PIX? . . or some other solution ?&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 08:07:05 GMT</pubDate>
    <dc:creator>swbruce21</dc:creator>
    <dc:date>2020-02-21T08:07:05Z</dc:date>
    <item>
      <title>PIX blocks Windows Server 2003 EDNS0(DNS) replies.</title>
      <link>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402244#M558780</link>
      <description>&lt;P&gt;PIX Firewall earlier than version 6.3(2) block dns query responses if query comes from Server 2003 and the external DNS server supports EDNSO.  Microsoft's workaround of disabling DNS-Probes did not solve the problem.  Short of updating the IOS is there a way to change the DNS-UDP packet size limit that is currently set on PIX? . . or some other solution ?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:07:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402244#M558780</guid>
      <dc:creator>swbruce21</dc:creator>
      <dc:date>2020-02-21T08:07:05Z</dc:date>
    </item>
    <item>
      <title>Re: PIX blocks Windows Server 2003 EDNS0(DNS) replies.</title>
      <link>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402245#M558782</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In PIX OS 6.3, it is possible to change the maximum DNS packet length using "fixup protocol" command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;fixup protocol dns maximum-length &lt;LENGTH&gt;&lt;/LENGTH&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_command_reference_chapter09186a00801727a8.html#wp1067379" target="_blank"&gt;http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_command_reference_chapter09186a00801727a8.html#wp1067379&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Or disabling dns fixup altogether (no fixup protocol dns)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't think there is any workaround with OS 6.2 and earlier, since the "DNS Guard" feature is hard-coded with no knobs for tweaking.&lt;/P&gt;&lt;P&gt;These threads are related to the same issue:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;forum=Security&amp;amp;topic=Firewalling&amp;amp;CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd75208" target="_blank"&gt;http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;forum=Security&amp;amp;topic=Firewalling&amp;amp;CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd75208&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;forum=Security&amp;amp;topic=Firewalling&amp;amp;CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd7c059" target="_blank"&gt;http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;forum=Security&amp;amp;topic=Firewalling&amp;amp;CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd7c059&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Mustafa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 May 2005 17:34:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402245#M558782</guid>
      <dc:creator>mhussein</dc:creator>
      <dc:date>2005-05-01T17:34:20Z</dc:date>
    </item>
    <item>
      <title>Re: PIX blocks Windows Server 2003 EDNS0(DNS) replies.</title>
      <link>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402246#M558785</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had the same problem and resolved it back in November using this procedure. Make sure you do it on BDC also. Stop/Restart DNS service or reboot domain controllers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For those customers using the Microsoft Windows 2003 Server's DNS&lt;/P&gt;&lt;P&gt;application, you must first install the dnscmd.exe command-line tool&lt;/P&gt;&lt;P&gt;from the Microsft Windows 2003 Server CD-ROM's Support Tools.  Once&lt;/P&gt;&lt;P&gt;this is installed, open a DOS command prompt window and type:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;dnscmd /config /enableednsprobes 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will turn off EDNS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If at a future time the customer upgrades their firewall application&lt;/P&gt;&lt;P&gt;to support EDNS, running "dnscmd /config /enableednsprobes 1" will&lt;/P&gt;&lt;P&gt;turn EDNS back on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 May 2005 13:34:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402246#M558785</guid>
      <dc:creator>sweaver</dc:creator>
      <dc:date>2005-05-02T13:34:36Z</dc:date>
    </item>
    <item>
      <title>Re: PIX blocks Windows Server 2003 EDNS0(DNS) replies.</title>
      <link>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402247#M558787</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks,  I mentioned in my question that I had disabled dns probes.  I found some newsgroups that indicated that in some case the problem would persist as it had in mine. I am glad it solve your problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 May 2005 18:00:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402247#M558787</guid>
      <dc:creator>swbruce21</dc:creator>
      <dc:date>2005-05-02T18:00:48Z</dc:date>
    </item>
    <item>
      <title>Re: PIX blocks Windows Server 2003 EDNS0(DNS) replies.</title>
      <link>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402248#M558788</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank You - very helpful&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 May 2005 18:17:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-blocks-windows-server-2003-edns0-dns-replies/m-p/402248#M558788</guid>
      <dc:creator>swbruce21</dc:creator>
      <dc:date>2005-05-02T18:17:16Z</dc:date>
    </item>
  </channel>
</rss>

