Server Fault is a question and answer site for system and network administrators. 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

On my local Ubuntu 10.04 dev machine, if I do a wget for a web address such as "wget", it gets stuck on "Resolving" for up to 30 seconds before the response is received. If I type into a browser, the response is near instant.

I have a similar experience using urllib.urlopen() in python, and file_get_contents() in php.

The reason I want to fix this issue is for testing code that accesses web services on my local dev machine (web service requests always seem to take up to 30 seconds which makes development slow and painful)

Any clues as to what might be causing this? How can I diagnose the problem?

share|improve this question
Using wget -4 took care of the problem as it forces wget to use IPv4 only (same as your browser). – ADTC Dec 5 '14 at 7:14

Google finds a number of reports that Ubuntu 10.4 has DNS timeout issues because it uses ipv6 (and the rest of your network does not, so you need to wait for the ipv6 lookup to timeout).

This might explain why your browser is faster, if it is configured not to use ipv6 for name resolution.

See, for example:

share|improve this answer

The 30 seconds delay sounds like a DNS timeout so check /etc/resolv.conf (especially the first-named DNS server).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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