<?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: localhost entry in /etc/hosts in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/localhost-entry-in-etc-hosts/m-p/6232671#M529414</link>
    <description>&lt;P&gt;I think I'd like to ask why they need a FQDN for a loopback address.&lt;/P&gt;</description>
    <pubDate>Thu, 10 Oct 2013 20:58:17 GMT</pubDate>
    <dc:creator>RJHall</dc:creator>
    <dc:date>2013-10-10T20:58:17Z</dc:date>
    <item>
      <title>localhost entry in /etc/hosts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/localhost-entry-in-etc-hosts/m-p/6232541#M529413</link>
      <description>&lt;P&gt;We have HPUX servers on 11.31.&amp;nbsp; Our localhost enty is in this format which I kinda use for years now.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;127.0.0.1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; localhost&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; loopback&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There were recent changes on the DNS managed by another support group. Their recommendation is&amp;nbsp; for us to create an entry&amp;nbsp; something like:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;127.0.0.1 localhost&amp;nbsp; localhost.ourcompany.org&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What do you think?&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Thanks!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;P.S. This thread has been moved from HP-UX &amp;gt; System Administration to HP-UX &amp;gt; networking.&lt;BR /&gt;-HP Forum Moderator&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2013 08:05:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/localhost-entry-in-etc-hosts/m-p/6232541#M529413</guid>
      <dc:creator>f. halili</dc:creator>
      <dc:date>2013-10-11T08:05:04Z</dc:date>
    </item>
    <item>
      <title>Re: localhost entry in /etc/hosts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/localhost-entry-in-etc-hosts/m-p/6232671#M529414</link>
      <description>&lt;P&gt;I think I'd like to ask why they need a FQDN for a loopback address.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 20:58:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/localhost-entry-in-etc-hosts/m-p/6232671#M529414</guid>
      <dc:creator>RJHall</dc:creator>
      <dc:date>2013-10-10T20:58:17Z</dc:date>
    </item>
    <item>
      <title>Re: localhost entry in /etc/hosts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/localhost-entry-in-etc-hosts/m-p/6232747#M529415</link>
      <description>&lt;P&gt;It's just another alias to the IP address. The requisite names are already there so the extra one won't create any problems. Somebody probably Googled localhost and found an obscure document that suggests that an FQDN does something useful.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 23:48:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/localhost-entry-in-etc-hosts/m-p/6232747#M529415</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2013-10-10T23:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: localhost entry in /etc/hosts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/localhost-entry-in-etc-hosts/m-p/6233177#M529416</link>
      <description>Thanks for the comments!</description>
      <pubDate>Fri, 11 Oct 2013 12:19:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/localhost-entry-in-etc-hosts/m-p/6233177#M529416</guid>
      <dc:creator>f. halili</dc:creator>
      <dc:date>2013-10-11T12:19:58Z</dc:date>
    </item>
  </channel>
</rss>

