<?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 names and PIX in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/names-and-pix/m-p/23391#M673814</link>
    <description>&lt;P&gt;In my previous firewall I was able to DNS records which was helpful as we only have a few names to provide publicly.  But now that I am setting a pix525 I realize this service is not available.  I do not want to want to have my service providor advertising these names as the addresses may change often and I would rather avoid contacting them.  I do not want to use the W2K active directory DNS for public addresses.  So I am whittling myself down to building a box just to handle five name translations.  Am I overlooking an obvious remedy here?&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 05:49:11 GMT</pubDate>
    <dc:creator>r.barnes</dc:creator>
    <dc:date>2020-02-21T05:49:11Z</dc:date>
    <item>
      <title>names and PIX</title>
      <link>https://community.cisco.com/t5/network-security/names-and-pix/m-p/23391#M673814</link>
      <description>&lt;P&gt;In my previous firewall I was able to DNS records which was helpful as we only have a few names to provide publicly.  But now that I am setting a pix525 I realize this service is not available.  I do not want to want to have my service providor advertising these names as the addresses may change often and I would rather avoid contacting them.  I do not want to use the W2K active directory DNS for public addresses.  So I am whittling myself down to building a box just to handle five name translations.  Am I overlooking an obvious remedy here?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 05:49:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/names-and-pix/m-p/23391#M673814</guid>
      <dc:creator>r.barnes</dc:creator>
      <dc:date>2020-02-21T05:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: names and PIX</title>
      <link>https://community.cisco.com/t5/network-security/names-and-pix/m-p/23392#M673841</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only other workaround I can think of is using a HOSTS file on each pc.  Although, this could be an administrative nightmare for you. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good Luck. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Aug 2001 19:44:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/names-and-pix/m-p/23392#M673841</guid>
      <dc:creator>j-block</dc:creator>
      <dc:date>2001-08-07T19:44:08Z</dc:date>
    </item>
  </channel>
</rss>

