"ping localhost" return a valid IP address, well at least not 127.0.0.1

druuna · 11-22-2010, 02:58 AM

Hi,

Looking at all the info you have given so far this seems to be your setup:

- Your PC has IP 192.168.1.33 (and 127.0.0.1 by convention)
- Your modem/router has IP 192.168.1.1 (and has a connection to the internet)

- The /etc/nsswitch.conf output is correct.

- Your /etc/hosts file should at least contain the following:

Code:

127.0.0.1         localhost.localdomain   localhost
192.168.1.33      mypc.myplace.com        mypc
192.168.1.1       router.myplace.com      router

- Your resolv.conf should look like this:

Code:

search myplace.com
nameserver 127.0.0.1
nameserver 192.168.1.1

mypc and the myplace.com are examples.

It seems that your hostname is localhost (root@localhost), which you should change to mypc. Have a look here: 28.1.22. /etc/sysconfig/network

Here's a link that gives you a good overview of the files you need to look at: 14.1. Network Configuration Files

Hope this helps.

@frankbell:

Code:

127.0.1.1	[localdomain]	tuna
192.168.1.5     [localdomain]   tuna

That is incorrect!!

If you use tuna it will _always_ point to 127.0.1.1
If a hostname -> ip translation is done it will quit when it finds the first hit, so it will never reach the 192.168.1.5 entry.

vbekker · 11-22-2010, 09:26 AM

Quote:

Originally Posted by tommyttt

This indicates the DNS(nameserver) is on your gateway. Is that correct? Are you providing your own DNS? If not, the nameserver needs to point to your DNS provider.

Tom

That is correct Tom, the router is also the DNS server.

jwl17330536 · 11-22-2010, 11:39 AM

What is at the 192.168.1.1 address? I'm assuming this is your gateway. (wireless router perhaps) Regardless of the device you need to see what the nameservers it is using. Can you post the output of the DNS that 192.168.1.1 is using?

jefro · 11-22-2010, 04:20 PM

Oppps.

frankbell · 11-22-2010, 07:21 PM

Quote:

Originally Posted by druuna

@frankbell:

Code:

127.0.1.1	[localdomain]	tuna
192.168.1.5     [localdomain]   tuna

That is incorrect!!

If you use tuna it will _always_ point to 127.0.1.1
If a hostname -> ip translation is done it will quit when it finds the first hit, so it will never reach the 192.168.1.5 entry.

Thanks. Will change it straightaway.

(One of the things I like about this place is that I learn stuff even when I don't expect to.)

vbekker · 11-23-2010, 09:04 AM

Yes, the DNS server is on the router as well. I think i figured out my problem. "ping localhost" returned 208.68.143.55 since i fatfingered my /etc/hosts file 127.0.0.1 entry, but "ping balhgarbageblah" also returned 208.68.143.55...which seems to be the address of a web server that my ISP hosts...any requests that it cannot resolve, it returns this IP...The webpage contains what i typed in to the address bar as search terms. Not sure how i can disable that.

jwl17330536 · 11-23-2010, 10:22 AM

I would use google's dns if you want to get around using your ISP's redirects.

http://code.google.com/speed/public-dns/

You can either configure your linux box to use it via your /etc/resolve, or configure your dhcp server (192.168.1.1 router in your case) to use the google dns which would then propogate the dns.