Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My system is debian 6.0. Both debian default brower and chrome don't work. The error is name resolution failed(code:137). I can ping and update software in gnome terminal.

Yesterday I installed pptp-linux, and pptp did work, I also could surf internet by chrome. Today I can't surf internet by browsers. after I remove pptp-linux, it still exist.

Have you encountered it?

share|improve this question

closed as too localized by Michael Mrozek May 24 '12 at 13:45

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Did you restart Chrome? On some systems, each program reads the DNS (name resolution) configuration when it starts, and doesn't see configuration changes after it's started. I don't know if this applies to a modern Linux system. – Gilles Jun 28 '11 at 11:24
duplicate from here. – Philomath Jul 29 '11 at 7:07
@Gilles Only Chrome 15 includes a built in DNS client and it must be enabled by flags. – Steve-o Aug 28 '11 at 4:33
You could try using Google's DNS? – n0pe Oct 27 '11 at 5:47

I found the issue. when executing the browers in root, I can surf internet. I don't know why.

share|improve this answer
lol, maybe some software has prevented you from doing something very stupid... browsing as root. – xenoterracide Jun 29 '11 at 3:53
@xenoterracide♦ that's the exact opposite of what was posted. – Steve-o Aug 28 '11 at 4:30
If this still happens, can you try getting an strace of chrome (strace chrome) and look for the open() calls, then check the permissions and ownership of the called files. A possible explanation would be that some file chrome -- for some reason -- uses to resolve names is not available to anyone but UID=0. – njsg Feb 14 '12 at 19:22

Not the answer you're looking for? Browse other questions tagged or ask your own question.