Date: Mon, 7 Jul 1997 07:47:16 -0400 (EDT) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!MX.BA-Stuttgart.De!helbig, ponds!lakes.water.net!rivers Cc: ponds!freefall.cdrom.com!freebsd-hackers Subject: Re: 127.1 and "localhost" (name resolution problem.) Message-ID: <199707071147.HAA01484@lakes.water.net>
next in thread | raw e-mail | index | archive | help
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 -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707071147.HAA01484>