Loopback issues

Hi:

I am having a rather confusing issue regarding my loopback address. The
computer has a 10.x.x.x address on its eth0 interface which is connected
to a Linksys router's LAN port

The ifconfig command shows that my loopback address is 127.0.0.1. My
DNS resolver shows that this is still the case. The /etc/host files
shows that the localhost is 127.0.0.1.

nslookup localhost and nslookup localhost.localdomain both show up as
127.0.0.1.

however when I attempt to ping typing this command

ping localhost

It shows that it is pinging my border router's WAN IP address instead of
the loopback address. I can verify that there is no IP masqurading
going on as there is no such entry in the iptables.

Any ideas as to what might be going on here?

Peter wrote:
> Hi:
>
> I am having a rather confusing issue regarding my loopback address. The
> computer has a 10.x.x.x address on its eth0 interface which is connected
> to a Linksys router's LAN port
>
> The ifconfig command shows that my loopback address is 127.0.0.1. My
> DNS resolver shows that this is still the case. The /etc/host files
> shows that the localhost is 127.0.0.1.
>
> nslookup localhost and nslookup localhost.localdomain both show up as
> 127.0.0.1.
>
> however when I attempt to ping typing this command
>
> ping localhost
>
> It shows that it is pinging my border router's WAN IP address instead of
> the loopback address. I can verify that there is no IP masqurading
> going on as there is no such entry in the iptables.
>
> Any ideas as to what might be going on here?

There are a huge number of possibilities. Doing an 'strace' on the ping
might help. For example:

You might be in the domain 'mydomain.com' and ping might be trying
'localhost.mydomain.com' first.

You might be using 'nscd' and it might have some other value for
'localhost' stuck in its cache.

Your resolver may be configured to use something else before /etc/host
or DNS.

DS

David Schwartz wrote:

>
> You might be in the domain 'mydomain.com' and ping might be trying
> 'localhost.mydomain.com' first.
>
This is exactly the case.... it is appending domain name to the localhost.

the order in resolving is as follows
hosts
dns
infact when I attempt to ping it this is exactly the case. My problem
is that the system mails a report to root@localhost which I am not
receiving.

Okay!! fixed the issue.

Peter wrote:
> Okay!! fixed the issue.

Which was? Or is it a secret?