<?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 DMZ address resolution in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-dmz-address-resolution/m-p/14982#M686797</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can try hosts file solution if the application is running on a server that is NOT running DNS. Add your DMZ host names with their local IP to the hosts file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even for the DNS server hosts file may be used at a higher priority for resolver but but external DNS queries may be answered from the DNS databases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This solution is suitable for only a few servers. If you have several computers consider running an internal DNS which resolves the DMZ names to local IP and forward/resolve the rest to global IP. The other will continue to serve the public accesses from DMZ.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Jan 2002 21:34:27 GMT</pubDate>
    <dc:creator>torkun</dc:creator>
    <dc:date>2002-01-17T21:34:27Z</dc:date>
    <item>
      <title>PIX DMZ address resolution</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-address-resolution/m-p/14980#M686795</link>
      <description>&lt;P&gt;My external DNS servers are on a PIX DMZ interface and they support multiple Web and Application servers on the same phyical subnet.  When one of these servers attempts to access a site ON THE SAME PHYSICAL SUBNET, the DNS query resolves to an external address and the connection fails.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have an ALIAS statement but this does not work in this instance becuase the lookup does not go through the PIX.  If I use NSLOOKUP and attach to a DNS server on the outside of the PIX, the ALIAS commands takes over and things work properly.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I suppose I could make these servers use someone elses DNS (external to the PIX), but I'd rather use my external DNS servers.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 05:56:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-address-resolution/m-p/14980#M686795</guid>
      <dc:creator>prpalmquist</dc:creator>
      <dc:date>2020-02-21T05:56:12Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ address resolution</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-address-resolution/m-p/14981#M686796</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The following link has some ideas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/110/pixfaq.shtml#Q15" target="_blank"&gt;http://www.cisco.com/warp/public/110/pixfaq.shtml#Q15&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2002 13:22:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-address-resolution/m-p/14981#M686796</guid>
      <dc:creator>turnbull</dc:creator>
      <dc:date>2002-01-15T13:22:46Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ address resolution</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-address-resolution/m-p/14982#M686797</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can try hosts file solution if the application is running on a server that is NOT running DNS. Add your DMZ host names with their local IP to the hosts file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even for the DNS server hosts file may be used at a higher priority for resolver but but external DNS queries may be answered from the DNS databases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This solution is suitable for only a few servers. If you have several computers consider running an internal DNS which resolves the DMZ names to local IP and forward/resolve the rest to global IP. The other will continue to serve the public accesses from DMZ.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jan 2002 21:34:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-address-resolution/m-p/14982#M686797</guid>
      <dc:creator>torkun</dc:creator>
      <dc:date>2002-01-17T21:34:27Z</dc:date>
    </item>
  </channel>
</rss>

