Comment 386 for bug 417757

Just like Casey I am experiencing the same problem on F12.

Clipper:~ $ ping peach.mycompany.com
PING peach.mycompany.com (10.26.1.61) 56(84) bytes of data.
64 bytes from peach.mycompany.com (10.26.1.61): icmp_seq=1 ttl=63 time=0.267 ms
64 bytes from peach.mycompany.com (10.26.1.61): icmp_seq=2 ttl=63 time=0.311 ms
^C
--- peach.mycompany.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1371ms
rtt min/avg/max/mdev = 0.267/0.289/0.311/0.022 ms
Clipper:~ $ ssh peach.mycompany.com
ssh: Could not resolve hostname peach.mycompany.com: No address associated with hostname

Here is the output from Wireshark when ssh command is issued:

24921 4305.188943 10.4.1.236 10.1.1.151 DNS Standard query A peach.mycompany.com
24922 4305.188983 10.4.1.236 10.1.1.151 DNS Standard query AAAA peach.mycompany.com
24923 4305.189460 10.1.1.151 10.4.1.236 DNS Standard query response A 10.26.1.61
24924 4305.189475 10.1.1.151 10.4.1.236 DNS Standard query response

The only way for me to fix this problem is to put the following line in /etc/hosts
10.26.1.61 peach

I should mention that this problem is _not_ unique to this network - the F12 machine is a laptop and I can see this problem at work as well as at home. It does not happen all the time but often enough to be annoying. Not sure what's the trigger.

Clipper:~ $ rpm -qa |grep glibc
glibc-2.11.1-4.i686
glibc-2.11.1-4.x86_64
glibc-headers-2.11.1-4.x86_64
glibc-common-2.11.1-4.x86_64
glibc-devel-2.11.1-4.x86_64
glibc-debuginfo-2.11.1-1.x86_64

Let me know if I can help in anyway to debug it.