[ale] Resolving

[Jason Lynn]

How is 127.0.0.1 resolved?  For instance, interface "lo" has 127.0.0.1 IP 
associated with it, but interface "eth0" also has an IP (192.168.0.1) 
associated with it.  If you can ping 127.0.0.1, I would think that you would 
also be able to ping 192.168.0.1.  (I also don't think that pinging 
127.0.0.1 is working for me either... but I can't say for sure right now).
>
>
>I'm used to seeing distros coming out-of-the-box with an /etc/hosts with
>one line that links "localhost" to 127.0.0.1.
>
>- Jeff
>
>Jason Lynn wrote:
> >
> > This is most likely a stupid question, but...
> > Since my cable modem has been down, I have been unable to resolve
> > "localhost" and even the IP address on my internal NIC.  This may have 
>been
> > caused because I've been "tweaking" a few things.  :)  My question is, 
>if
> > I'm not running named, how does my computer resolve "localhost" and even 
>my
> > local IP address?  Would it normally go to the (now unreachable) DNS 
>servers
> > to resolve "localhost"?  How about my internal IP... the DNS server 
>knows
> > nothing about my internal addresses, so how are they resolved?  And why
> > aren't they being resolved now (ie pinging 192.168.0.1 from 192.168.0.1
> > isn't working, though pinging 192.168.0.1 from 192.168.0.2 IS working)?
> > Like I said... stupid question... but I'd appreciate any insight.  
>Thanks.
> >
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at 
>http://explorer.msn.com/intl.asp
> >
> > --
> > To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message 
>body.

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.