Comment 366 for bug 417757

Created attachment 354195
wireshark capture

I agree it's hard to understand. It is not fixed by
"sudo /etc/init.d/iptables stop". The capture was made
on the client machine 172.22.2.7. It happens for all domains,
unless I add them to the /etc/hosts file. I can ping and
dig them just fine. I'm attaching an unfiltered capture
of this session...

  [root@jibsheet ~]# rpm -q glibc
  glibc-2.10.1-3.i686
  [root@jibsheet ~]# iptables-save
  # Generated by iptables-save v1.4.3.1 on Fri Jul 17 13:48:59 2009
  *filter
  :INPUT ACCEPT [534:96543]
  :FORWARD ACCEPT [0:0]
  :OUTPUT ACCEPT [136:21713]
  COMMIT
  # Completed on Fri Jul 17 13:48:59 2009
  [root@jibsheet ~]# ping -c 1 google.com
  PING google.com (74.125.45.100) 56(84) bytes of data.
  64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=1 ttl=54 time=39.4 ms

  --- google.com ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 51ms
  rtt min/avg/max/mdev = 39.430/39.430/39.430/0.000 ms
  [root@jibsheet ~]# ssh -v google.com
  OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: Applying options for *
  ssh: Could not resolve hostname google.com: Temporary failure in name resolution
  [root@jibsheet ~]# getent ahosts fdd.com
  [root@jibsheet ~]# getent ahosts google.com

The machine is newly installed F11, with updates applied by yum
after adding hostnames to /etc/hosts. I've added vlc
from rpmfusion, and now your glibc, but basically nothing
else.

Trying again with glibc-2.10.1-2 produces the same
results as -3, i.e. no ICMP. I'm sorry to be such trouble.