<?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: /etc/hosts question??? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900369#M578366</link>
    <description>Hi &lt;BR /&gt;&lt;BR /&gt;127.0.0.1 localhost loopback &lt;BR /&gt;loopback is an internal address that uses the TCP stack, but no network card .&lt;BR /&gt;&lt;BR /&gt;besacley the localhost and the loopback are the same and there are for internal network .&lt;BR /&gt;&lt;BR /&gt;dont remove this line from the /etc/hosts . &lt;BR /&gt;</description>
    <pubDate>Sun, 09 Feb 2003 14:59:52 GMT</pubDate>
    <dc:creator>eran maor</dc:creator>
    <dc:date>2003-02-09T14:59:52Z</dc:date>
    <item>
      <title>/etc/hosts question???</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900368#M578365</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;May someone can explain, why I need line:&lt;BR /&gt;# HP Loopback&lt;BR /&gt;127.0.0.1  localhost loopback&lt;BR /&gt;&lt;BR /&gt;at the /etc/hosts file? And I read, that I shouldn't change this string. Why?&lt;BR /&gt;&lt;BR /&gt;Thank you for explanation!&lt;BR /&gt;</description>
      <pubDate>Sun, 09 Feb 2003 14:42:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900368#M578365</guid>
      <dc:creator>yank</dc:creator>
      <dc:date>2003-02-09T14:42:29Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/hosts question???</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900369#M578366</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;127.0.0.1 localhost loopback &lt;BR /&gt;loopback is an internal address that uses the TCP stack, but no network card .&lt;BR /&gt;&lt;BR /&gt;besacley the localhost and the loopback are the same and there are for internal network .&lt;BR /&gt;&lt;BR /&gt;dont remove this line from the /etc/hosts . &lt;BR /&gt;</description>
      <pubDate>Sun, 09 Feb 2003 14:59:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900369#M578366</guid>
      <dc:creator>eran maor</dc:creator>
      <dc:date>2003-02-09T14:59:52Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/hosts question???</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900370#M578367</link>
      <description>A bit of follow up to the great advice above.&lt;BR /&gt;&lt;BR /&gt;There may be additional network information in the file that you can change if you know your network configuration.&lt;BR /&gt;&lt;BR /&gt;loopback always gets used.&lt;BR /&gt;&lt;BR /&gt;If network resolution isn't working based on the info in /etc/hosts it could be because you've set resolution to work elsewhere.&lt;BR /&gt;&lt;BR /&gt;It is common to have a file called /etc/nsswitch.conf which can tell the server to resolve elsewhere first.&lt;BR /&gt;&lt;BR /&gt;Here is mine and what it says.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;hosts:        dns[notfound=continue unavail=continue tryagain=continue] files&lt;BR /&gt;&lt;BR /&gt;This means, look for network host resolution on a dns server first. then files, wich is /etc/hosts&lt;BR /&gt;&lt;BR /&gt;dns resolution is controlled by what dns servers you machine uses, which could be but doesn't have to be itself.&lt;BR /&gt;&lt;BR /&gt;Here is an example of the /etc/resolv.conf file which controls where your box looks for dns resolution.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;[4243#] more /etc/resolv.conf&lt;BR /&gt;domain juf.net&lt;BR /&gt;nameserver 10.1.10.39&lt;BR /&gt;nameserver 10.1.10.45&lt;BR /&gt;nameserver 10.1.10.47&lt;BR /&gt;&lt;BR /&gt;This says I'm part of domain juf.net and I look to three nameservers for hos resolution.&lt;BR /&gt;&lt;BR /&gt;SEP&lt;BR /&gt;</description>
      <pubDate>Sun, 09 Feb 2003 20:38:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900370#M578367</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-02-09T20:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/hosts question???</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900371#M578368</link>
      <description>In direct explanation of your question.....&lt;BR /&gt;&lt;BR /&gt;localhost and loopback are aliases for the IP address 127.0.0.1. When a program or script refers to an alias it actually gets 127.0.0.1&lt;BR /&gt;&lt;BR /&gt;127.0.0.1 is defined everywhere in the known universe as an IP address internal to your machine. This definition is part of the fabric of the universe along with the speed of light and why bread falls butter side down.&lt;BR /&gt;</description>
      <pubDate>Sun, 09 Feb 2003 21:15:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900371#M578368</guid>
      <dc:creator>paul courry</dc:creator>
      <dc:date>2003-02-09T21:15:12Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/hosts question???</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900372#M578369</link>
      <description>Forgot the Why..........&lt;BR /&gt;&lt;BR /&gt;Touch that line and you may possibly screw up your machine forever. There are billions and billions of programs and scripts which use the alias localhost or loopback instead of the IP address 127.0.0.1&lt;BR /&gt;&lt;BR /&gt;Remove it and all those programs and scripts stop working.</description>
      <pubDate>Sun, 09 Feb 2003 21:18:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900372#M578369</guid>
      <dc:creator>paul courry</dc:creator>
      <dc:date>2003-02-09T21:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/hosts question???</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900373#M578370</link>
      <description>Thank you for yours explanations!&lt;BR /&gt;But, when I use netstat -rn command I see two Interfaces Lo0 and Lan0(actually I had one - Lan0). What the Lo0 means (it's used by loopback, and has a biggest number of USE)?&lt;BR /&gt;The output is:&lt;BR /&gt;&lt;BR /&gt;netstat -rn&lt;BR /&gt;Routing tables&lt;BR /&gt;Destination     Gateway         Flags   Refs     Use  Interface  Pmtu PmtuTime&lt;BR /&gt;127.0.0.1       127.0.0.1       UH         8     601  lo0        4608&lt;BR /&gt;192.168.20.61   127.0.0.1       UH        10  361827  lo0        4608&lt;BR /&gt;default         192.168.20.1    UG         0       4  lan0       1500&lt;BR /&gt;192.168.20      192.168.20.61   U          1    2536  lan0       1500&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Feb 2003 08:11:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900373#M578370</guid>
      <dc:creator>yank</dc:creator>
      <dc:date>2003-02-10T08:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/hosts question???</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900374#M578371</link>
      <description>Lo0 is your loopback interface.  The one everyone is telling you not to mess with. As you have noticed it is a very popular interface.  All of Paul's "...billions and billions..." of programs are busy using it.  The loopback is used because it is an easy way to communicate from one process to another on the same machine without having to worry about messy things like how the memory is laid out.  Traffic to the loopback interface travels down the TCP/IP stack like any other but before it hits the NIC it is shunted back up into the incoming stream.  &lt;BR /&gt;&lt;BR /&gt;lan0 is your real NIC.  The lan = LAN part should be clear.  The 0 comes because programmers don't count 1, 2, 3 like normal people but always start with 0. &lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Mon, 10 Feb 2003 18:01:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-hosts-question/m-p/2900374#M578371</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2003-02-10T18:01:44Z</dc:date>
    </item>
  </channel>
</rss>

