Fails to try next server when resolving domain name if primary server returns no recursion available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wget (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: wget
In a situation where DNS servers misbehave, wget fails to try the next server if the primary returns "recursion not available" on a particular domain name, even if the secondary DNS server is able to answer the query.
See the output of nslookup and wget in such a situation:
bruno@nuuk:~$ nslookup www.camino.uk.com
;; Got recursion not available from 217.13.128.17, trying next server
Server: 83.218.143.36
Address: 83.218.143.36#53
Non-authoritative answer:
www.camino.uk.com canonical name = camino.uk.com.
Name: camino.uk.com
Address: 67.222.99.135
bruno@nuuk:~$ wget www.camino.uk.com
--2010-07-08 14:36:57-- http://
Resolving www.camino.
wget: unable to resolve host address `www.camino.uk.com'
Expected behaviour: if nslookup is able to resolve the domain name, I would expect that wget and any other HTTP client be able to do the same rather than exit with an error.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: wget 1.12-1.1ubuntu2
ProcVersionSign
Uname: Linux 2.6.32-23-generic i686
Architecture: i386
Date: Wed Jul 14 15:13:12 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: wget
Closing that outdated report as EOL has been reached long time ago