src/lib/libc/net/res_query.c, branch release/5.4.0FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=release%2F5.4.02004-04-21T09:50:52ZUnbreak world.2004-04-21T09:50:52ZRuslan Ermilovru@FreeBSD.org2004-04-21T09:50:52Zurn:sha1:2d695ed31d8e99ad6caf764014de5386e8493427MFdragonfly: resolver fix for timeouts on unqualified hostnames2004-04-21T00:56:38ZNate Lawsonnjl@FreeBSD.org2004-04-21T00:56:38Zurn:sha1:1cc11684ac8f4901edf2993aa6d5e2177b633d76
res_search only incremented got_servfail for h_errno == TRY_AGAIN *AND*
hp->rcode == SERVFAIL. However, there are cases such as timeouts where
rcode is not always set to SERVFAIL. This leads to inconsistent nameserver
operation during multi-domain and truncated dot searches, especially during
booting when portions of the network are being brought up simultanious with
dns lookups.
This patch attempts to correct the problem by unconditionally terminating
the search if TRY_AGAIN is returned (after res_query has gone through all
retries and name servers) instead of trying other domain elements in the
domain seach path.
This patch should fix reported problems (which I can reproduce) with some
NFS mounts failing during boot. This occured because mount_nfs thought the
host name lookup returned a definitive failure using a non-dotted host name
when, in fact, it timed out on the first part (host.search.domain.name) and
got a definitive host-not-found response on the second part (host.).
Generally speaking, search path name server timeouts can exceed 60 seconds
per element and most machines which consistently timeout on earlier portions
of a search path are effectively non-operational due to the imposed delays.
It is more important for DNS lookups to return the proper error code then
to be able to recover a valid lookup in later portions of the search path
in these situations.
Obtained from: DragonFly
MFC after: 3 weeks
Restore vendor ID.2003-03-03T01:12:24ZDavid E. O'Brienobrien@FreeBSD.org2003-03-03T01:12:24Zurn:sha1:c492fac74122a6f48dfe735f2e4cec75823fbc4dEliminate 61 warnings emitted at WARNS=2 (leaving 53 to go).2003-02-16T17:29:11ZJacques Vidrinenectar@FreeBSD.org2003-02-16T17:29:11Zurn:sha1:e0554a531f17f56167f978eddf29a09cc6ae9f32
Only warnings that could be fixed without changing the generated object
code and without restructuring the source code have been handled.
Reviewed by: /sbin/md5
Backout the increase of MAXPACKET from 1024 to 65536: it2002-09-15T04:23:20ZJacques Vidrinenectar@FreeBSD.org2002-09-15T04:23:20Zurn:sha1:7deb8a7ddd4693fef8940268a30a3927bfa104e6
broke pthreads.
Reported by: mbr, tjr
When using res_send/res_query/res_search, the caller must either2002-09-13T20:31:29ZJacques Vidrinenectar@FreeBSD.org2002-09-13T20:31:29Zurn:sha1:2e4dbbaa930e32c8768110b5888ed88c61c417a3
insure enough space is available for the response, or be prepared
to resize the buffer and retry as necessary.
Do the conservative thing and make sure enough space is available.
Reviewed by: silence on freebsd-audit
Fix syntax error which occurred when LIBC_SCCS was defined.2002-07-07T11:28:28ZRobert Drehmelrobert@FreeBSD.org2002-07-07T11:28:28Zurn:sha1:897ad22f040518e3e756665eeeb81ba0d9db14a4Fix the style of the SCM ID's.2002-03-22T21:53:29ZDavid E. O'Brienobrien@FreeBSD.org2002-03-22T21:53:29Zurn:sha1:333fc21e3cd79bca0c94d7722c5a56cb5ad078d1
I believe have made all of libc .c's as consistent as possible.
Remove 'register' keyword.2002-03-21T18:49:23ZDavid E. O'Brienobrien@FreeBSD.org2002-03-21T18:49:23Zurn:sha1:8fb3f3f68288ae2b1b53dd65e3dd673d83c80f4cImplement EDNS0 support, as EDNS0 support will be made mandatory for2001-06-10T20:25:24ZHajimu UMEMOTOume@FreeBSD.org2001-06-10T20:25:24Zurn:sha1:ce6282db3bc7b3deae846fd0757214c3814d3041
IPv6 transport-ready resolvers/DNS servers. Need careful configuration
when enable it. (default config is not affected).
See manpage for details.
XXX visible symbol __res_opt() is added, however, it is not supposed to be
called from outside, libc minor is not bumped.
Obtained from: KAME/NetBSD