static ip address not resolving names

[cannonfodder]

Using micro core 2.6.1.

Trying to set up a static ip.

Followed the instructions in http://forum.tinycorelinux.net/index.php?topic=2987.0...

I can ping my ISPs DNS IP but not www.google.com ('bad address').

That is, since I can ping IPs, my connection is fine but domain names are't being resolved.

[roberts]

What did you enter for DSN Name Servers?
What is in /etc/resolv.conf ? Typically the DNS IPs are supplied by your ISP.
If needed you can use public DNS servers, e.g.,

208.67.222.222
208.67.220.220

or

8.8.8.8
4.4.4.4

Just be sure you can ping them before trying to use them.

[gerald_clark]

The Google public DNS servers are
8.8.8.8 and 8.8.4.4.

[cannonfodder]

I can ping my ISP's DNS and 8.8.8.8 but not 4.4.4.4...

/etc/resolve.conf is identical to another machine running Tiny Core that CAN ping www.google.com.

No other machine on the LAN is unable to ping www.google.com.

Using DHCP, the problem machine CAN ping www.google.com.

[roberts]

As was pointed out the secondary DNS server is not 4.4.4.4 but 8.8.4.4.

[cannonfodder]

Even after modifying /etc/resolve.conf nameserver to read 8.8.4.4, problem persists.

I can ping IPs but domain name resolution does not happen if I set a static IP.

EXACT same setup (except for LAN IP) works on Tiny Core 1.3 or 1.4, whatever was current early summer 2009.

[roberts]

Not sure what you mean by LAN IP.
Is this behind a router?  Is your router setup to provide IPs and DNS?
Do you need to specify your static IP to your router? Perhaps peruse your router settings?

[cannonfodder]

Yes LAN IP means I'm behind a router. Computer experiencing problems is part of a Local Area Network.

There are three other PCs on this same LAN, including one running Tiny Core and it has a static Internet Protocol address. All but problem machine can ping domain names.

The problem machine running micro core 2.6.1. is set up in the exact same way as the PC running Tiny Core.

Logically, this points to a configuration or software problem on the PC running micro core.

Any one have any ideas?

[cannonfodder]

Since static IP gets set by /opt/bootlocal.sh, would it help to restart the networking daemon once Micro Core has finished loading and I've got a prompt?

If so, what command do you use in Tiny Core / Micro Core to restart network daemon?

I'm much more familiar with Debian / Ubuntu systems where this could be done by issuing sudo service network restart.

I've googled this issue and have found nothing illuminating. I have to assume that /etc/resolve is fine b/c other machines on the lan use the same nameserver and domain names manage to get resolved.

/etc/resolve.conf file aside, what else could possible cause this?

[gerald_clark]

There is no network daemon. Just bootlocal.sh
Are you sure you assigned a unique IP address in your local network?
What does ifconfig show?

[bmarkus]

What is the ouput of the 'ifconfig' and 'route' commands and what is the IP address of your router?

[cannonfodder]

I think I have an idea why I can't get static IP to resolve on the one machine.

Turns out roberts may have hit the nail on the head when he mentioned router settings.

I tried Tiny Core 1.3 on the machine not resolving and the problem persisted. I then tried the same Tiny Core 1.3 CD on another machine already running Tiny Core with a working static IP, used its modified /opt/bootlocal.sh to set static IP and it too COULD ping domain names.

Logically, my static IP problems now look to be unrelated to Tiny Core.

The difference between the setup of the two machines? I have a WDS set up using two Linksys routers. One router runs dd-wrt, the other default Linksys software. The PC with a working static IP is connected to the dd-wrt gateway.

The dd-wrt gateway is dns-masq enabled, the plain Linksys router is not.

If my assumptions are correct and dns-masq is responsible for getting the PC with the working static IP to resolve, I suppose I could look into enabling the same function in my other router.

Thing is, /etc/resolve.conf should be working.

Any further input or suggestions is more than welcome...

[cannonfodder]

After a fresh round of troubleshooting, I'm having to rethink some of my conclusions/assumptions.

Router or router configuration aren't the issue:

- The PC running Tiny Core 1.2 or 1.3 with correctly working static IP is a laptop. Whether this laptop is connected to one router or the other, domain names get resolved.

- The PC running Micro Core with incorrectly working static IP has multiple OSes on it. To wit, I have CrunchBang set up with correctly functioning static IP on this machine.

@ bmarkus:

With the laptop and PC side-by-side connected to the same router and with the former working as desired and the latter not, the results of ifconfig and route are identical except for internal IP address.

It would appear, then, to be a problem with configuration.

When I have more time, I'll start up Micro Core with nodhcp base norestore and try to run the eth0.sh script one line at a time to see what happens....

[cannonfodder]

Happy to report that this problem has been SOLVED...

Embarrassed about the nature of the problem, however.

I was echoing nameserver info to /etc/resolve.conf and NOT /etc/resolv.conf