Re: [Bug-wget] Slow DNS resolve (5 seconds)

[Micah Cowan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Adrian Grajdeanu wrote:
> Notice realtime is 5 seconds and change. Five seconds are spent at the
> Resolving www.google.com...
> line before answers are provided.

The usual source of these sorts of problems is a dead nameserver. If
your /etc/resolv.conf has multiple nameservers listed, try removing the
first one (or check for a dead one by specifying the server explicitly
to dig).

> Similar request using curl is 5 seconds faster:

Typical builds of curl uses the custom DNS resolver c-ares, rather than
the system gethostbyname() or what have you. This makes it not
particularly suitable for comparison with Wget's resolution times, as
Wget uses the system utility functions. IIRC c-ares will send requests
to multiple servers at a time and process whichever result it gets the
fastest, whereas typical system implementations try servers successively
(meaning a 5-second-or-so delay for _every_ name resolution!).

- --
HTH,
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
http://micah.cowan.name/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkk0XTcACgkQ7M8hyUobTrGMogCfQ8TzQgYpL4alGfxx6K91Voqy
D0AAnRab8qhnM98HhGt3JQjMujRZ8eDS
=cZlp
-----END PGP SIGNATURE-----