From owner-freebsd-hackers Mon Jul 7 09:50:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA22924 for hackers-outgoing; Mon, 7 Jul 1997 09:50:49 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA22893 for ; Mon, 7 Jul 1997 09:50:44 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA02335; Mon, 7 Jul 1997 12:50:11 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 7 Jul 1997 12:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id HAA12365; Mon, 7 Jul 1997 07:38:52 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id HAA01484; Mon, 7 Jul 1997 07:47:16 -0400 (EDT) Date: Mon, 7 Jul 1997 07:47:16 -0400 (EDT) From: Thomas David Rivers Message-Id: <199707071147.HAA01484@lakes.water.net> To: ponds!MX.BA-Stuttgart.De!helbig, ponds!lakes.water.net!rivers Subject: Re: 127.1 and "localhost" (name resolution problem.) Cc: ponds!freefall.cdrom.com!freebsd-hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wolfgang writes: > > But - If I replace that line with: > > > > 127.0.0.1 localhost.water.net localhost > > > > > > Everything works fine. I suggest that, until this problem > > is fixed, we use 127.0.0.1 in any automated generation of > > You already fixed the problem :-) The ip address ``127.1'' is certainly > bogus. In 2.2.1, 2.2.2 or -current the ip address is correct. (i. e. > 127.0.0.1) > > > /etc/hosts... I'm not sure where mine came from; it could be an > > older installation (e.g. upgrades...) > > > > > If someone happens to be poking around in /etc/hosts resolution > > code; I'd be interested in knowning why this didn't work... > > Should it? Yes - I believe it should; and it's my understanding that 127.1 isn't bogus. It's my understanding that, if an IP quad wasn't complete, the missing components were filled with zero - from the middle. So: 127.1 => 127.0.0.1 127.10.1 => 127.0.10.1 127 => 127.0.0.0 It's a rarely exercised "feature" these days; but 127.1 does mean 127.0.0.1 and should work... (it used to work, anyway.) - Dave Rivers -