Actually, as I recall, 127.1 is a valid abbreviation for 127.0.0.1, and is
_not_ shorthand for network 127.1.0.0.  And, IIRC, 129.2.3 is also a valid
shorthand for 129.2.0.3 rather than for network 129.2.3.0.  Note that this
kind of abbreviation only works for Class A and B networks (first octet is
between 1 and 191).

As for the original problem, you might want to check your /etc/resolv.conf
file to make sure that it knows who your DNS servers are, and also make
sure it specifies a default domain and a lookup sequence.  Here's mine:

	domain whooppee.com			# our local domain
	lookup file bind		# check /etc/hosts first
	nameserver 127.0.0.1		# uncomment if named is local
	nameserver 204.188.125.5
	nameserver 204.188.125.8


On Mon, 30 Jun 1997, Bill Studenmund wrote:

> > 
> > At 2:43 PM -0400 6/30/97, tcjam wrote:
> > >Should I have 127.1 or 127.0.0.1 and would this be causing the "File
> > >exists" errors that I'm getting from route?
> > 
> > I am having the same problem.  I can't figure out what file it is
> > referencing.  Any insight would be welcome.
> 
> I think it's route poorly complaining about something. Do you have routed
> set up right? I normally leave routed off, but I'm not a server. :-)
> 
> > As far as the host file is concerned, everything I have read the addresses
> > should be complete.  i.e.  127.0.0.1
> 
> Yes. 127.1 is typically shorthand for the NETWORK 127.1.X.Y, not a host on
> the loopback's net.
> 
> Take care,
> 
> Bill
> 

-----------------------------------------------------------------------------
| Paul Goyette       | PGP Public Key fingerprint:  | E-mail addresses:     |
| Network Consultant |     0E 40 D2 FC 2A 13 74 A0  |  paul@whooppee.com    |
| and kernel hacker  |     E4 69 D5 BE 65 E4 56 C6  |  paul_goyette@ins.com |
-----------------------------------------------------------------------------