<?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: Host Alias in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839241#M90809</link>
    <description>Thank you all for your response.  One thing I am considering is to have the customer assign the drivers to a Class A (private) ip address.</description>
    <pubDate>Tue, 05 Nov 2002 18:11:42 GMT</pubDate>
    <dc:creator>Global Server Operation</dc:creator>
    <dc:date>2002-11-05T18:11:42Z</dc:date>
    <item>
      <title>Host Alias</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839237#M90805</link>
      <description>I have a customer that would like to assign four print drivers as alias to the server ip address. The server is a n4000 running 11.i. These drivers will are used to take print requests from the customer's website and direct them to a file on the server instead of going through the spooler.  I don't feel comfortable assigning four alias to the server ip/hostname.  Should there be any concerns I need to consider?</description>
      <pubDate>Tue, 05 Nov 2002 16:02:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839237#M90805</guid>
      <dc:creator>Global Server Operation</dc:creator>
      <dc:date>2002-11-05T16:02:11Z</dc:date>
    </item>
    <item>
      <title>Re: Host Alias</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839238#M90806</link>
      <description>You can have as many aliases as you like; I wouldn't consider that a security problem although this design seems a little hokey to me. From a security standpoint the aliases shouldn't be a problem because after all the hostnames could be bypassed altogether by using the IP address itself.&lt;BR /&gt;</description>
      <pubDate>Tue, 05 Nov 2002 16:07:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839238#M90806</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-11-05T16:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: Host Alias</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839239#M90807</link>
      <description>Seems like a very weird way to get this to work but the alias should work. Why do they not want to just assign each with its own ip address??</description>
      <pubDate>Tue, 05 Nov 2002 16:13:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839239#M90807</guid>
      <dc:creator>Ken Hubnik_2</dc:creator>
      <dc:date>2002-11-05T16:13:25Z</dc:date>
    </item>
    <item>
      <title>Re: Host Alias</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839240#M90808</link>
      <description>There shouldn't be any problem in defining aliases. One of the reasons why customer is directing them to the server instead of sending them to spooler can be that customer wants to go through the jobs before printing them if they are legit. Another reason can be that they are actually using the print-queue to pass the data to a program.&lt;BR /&gt;&lt;BR /&gt;But I am not, in any way, justifying anything!&lt;BR /&gt;:-)&lt;BR /&gt;&lt;BR /&gt;...Manjeet</description>
      <pubDate>Tue, 05 Nov 2002 17:55:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839240#M90808</guid>
      <dc:creator>Kellogg Unix Team</dc:creator>
      <dc:date>2002-11-05T17:55:57Z</dc:date>
    </item>
    <item>
      <title>Re: Host Alias</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839241#M90809</link>
      <description>Thank you all for your response.  One thing I am considering is to have the customer assign the drivers to a Class A (private) ip address.</description>
      <pubDate>Tue, 05 Nov 2002 18:11:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/host-alias/m-p/2839241#M90809</guid>
      <dc:creator>Global Server Operation</dc:creator>
      <dc:date>2002-11-05T18:11:42Z</dc:date>
    </item>
  </channel>
</rss>

