Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: #1 PCLinuxOS -- for laughs -> Ubuntu, Suse, Mepis
Posts: 315
Rep:
Do simple things ..
check your IP address (use ifconfig eth0 .. to see what's it at ..)
open a window to your router ..
something like .. 192.168.1.1 (it should show you that).
Make sure you have DHCP enabled on your port.
run ping to one ore two of your nodes .. like ping the router ... ping another machine on the network ... then start going towards yahoo .. or others that
would need to be resolved by dns ..
BUT THAT WON:T HAPPEN UNLESS YOU ARE USING DHCP .. or setting the DNS addresses by hand .. try DHCP .. it 'works for the whole world and will surely work for you.;
Don't pay attention to these these "route" command guys .. they are just making it unnecessarily complicated.. it's NOT NECESSARY.
Not trying to be mean but he did actually know and solve the problem.
/etc/resolv.conf is not updating or the router was misconfigured, which is a DNS problem. He started a dns server. (did not fix the problem but had a work around) It did work.
From his original resolv.conf file the contents are from dhcp but the nameserver looks wrong, which looks like the router needs the correct nameservers in it. Or he's firewalled the nameserver. So his local DNS works.
Last edited by DavidPhillips; 02-13-2005 at 10:26 PM.
what i think is that u should not depend on dhcp untill other ways are there
one simple example will be like when u are starting ur linux machine and if u depend on dhcp for ur IP address and if ur windows machine is not UP then u won't get an IP address and u will have to configure it with DHCP again after that win mahcine is up
also caching nameserver is good since u don't have to go anywhere to resolve ur IP address after they are cached and they will be resolved locally
also i think it is not easy , without using route coommand because i too have faced a lot of problems which were solved after i got a clearer picture using the route command
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.