DebianThis forum is for the discussion of Debian Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
On my new Debian Squeeze installation (kernel 2.6.26) I'm running into a problem with browsers. Apt-get can access the debian repositories just fine, and ping has no problem resolving hostnames. However, when I run konqueror or iceweasel and try to access any sites, the browsers can't resolve the domains (The browser could not find the host server for the provided address.)
My /etc/resolv.conf looks like this:
However, I doubt that the problem is with resolv.conf since ping can resolve any arbitrary existing domain name (I've tried google.com, linuxquestions.org, debian.org, and pandora.com).
I forgot to try accessing sites directly via IP earlier. Even when I attempt to load, say, 220.127.116.11 (google), I still get the "host cannot be found" error. I doubt also that this is a firewall issue, since internet access works fine on XP and slackware on the same box.
Thanks for taking the time to read and reply to this =).
Last edited by morganmcdermott; 05-29-2009 at 03:58 PM.
No, if that didn't work then DNS is not the issue. That is what the test has proven. Looks like now we either have incorrect proxy server.... Look at the proxy first, if you have one turned on, turn it off.
Or your tcp port is blocked somehow, pings go though a different port than web access.
*have you tried hitting refresh just in case, sometimes my firefox times out like that. My kid automaticly restarts the modem and I keep telling her just to hit refresh first...
Last edited by anarchyinc; 05-29-2009 at 04:19 PM.