Tiny Core Base > Micro Core

static ip address not resolving names

<< < (2/3) > >>

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?

Navigation

[0] Message Index

[#] Next page

[*] Previous page