Comment 11 for bug 326718

Hi "H" - Thank you for the attention; may I suggest filing a separate bug so we don't reenact the RedHat bug's confusion over multiple glibc versions? :}

To better understand your issue, it will help to post the versions of glibc installed on each machine - `dpkg-query -s libc6` will return this, if memory serves - and what each machine is using for a name server (contents of /etc/resolv.conf for each; contents of /etc/nsswitch.conf also).

I'm not familiar with the plug'n'play forwarding features of Ubuntu, if they're what you're using, but it can be easy to get into strange situations when using NAT, particularly if UDP packets are involved. You could have a resolver bug, but you could also have a NAT bug/misconfiguration that, for instance, is routing some responses to the laptop incorrectly at the expense of the desktop. If you are also using a software firewall on the desktop, that's another variable that can also accidentally block legitimate packets. Are you only having the problem with apt-get and other glibc resolver consumers, or does `dig` fail as well?

In my case, I am using a DNS server that is "known good" as far as not presenting any problems with 8.10 / libc6 "2.8~20080505-0ubuntu7" or BSD boxes on the same network, or to `dig` on the same machine, so I can at least claim to have identified specific new misbehavior between libc6 2.9-0ubuntu10 and the working libc6 2.8~20080505-0ubuntu7.