> Actually, you're almost always better off with TCP these days on
> virtually any protocol.  The "overhead" of TCP turns out to be more
> than offset by getting real congestion control.  An extremely
> unloaded LAN or something where you have very small transactions are
> the only (possible) exceptions.

Isn't that exactly what you have for DNS traffic to a nearby server?

And - regardless of what *should* happen - I've got a program that
hangs, every once in a while, when trying to do DNS lookups over TCP
(to a very local server, both hosts on my house LAN).  It appears to
drop into res_query and never come out.  I don't yet know more; I
haven't yet considered the problem important enough to investigate
further.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B