For some reason ping on a WAN address returns 100% packet loss when executed with `-c 1`, but with `-c 2`, there is 0% packet loss. This appears to be consistent across multiple networks and machines, but hosts on the local LAN do not appear to be affected.

Ping count=1 to google:

# ping -c 1 www.google.com
PING www.google.com (2607:f8b0:400b:802::2004) 56 data bytes

--- www.google.com ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


Now ping with count=2

# ping -c 2 www.google.com
PING www.google.com (2607:f8b0:400b:802::2004) 56 data bytes
64 bytes from yyz12s06-in-x04.1e100.net (2607:f8b0:400b:802::2004): icmp_seq=1 ttl=119 time=16.3 ms
64 bytes from yyz12s06-in-x04.1e100.net (2607:f8b0:400b:802::2004): icmp_seq=2 ttl=119 time=13.3 ms

--- www.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 13.326/14.788/16.250/1.462 ms


Ping with count=1 again to check if we have any sorts of arp or DNS lookup races or something like that:

# ping -c 1 www.google.com
PING www.google.com (2607:f8b0:400b:802::2004) 56 data bytes

--- www.google.com ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


Ping with count=1 using IP address:

# ping -c 1 2607:f8b0:400b:802::2004
PING 2607:f8b0:400b:802::2004 (2607:f8b0:400b:802::2004) 56 data bytes

--- 2607:f8b0:400b:802::2004 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


Ping with count=1 using IPv4 address:

# ping -c 1 142.251.33.164
PING 142.251.33.164 (142.251.33.164) 56(84) bytes of data.

--- 142.251.33.164 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


Ping with count=2 using IPv4 address:

# ping -c 2 142.251.33.164
PING 142.251.33.164 (142.251.33.164) 56(84) bytes of data.
64 bytes from 142.251.33.164: icmp_seq=1 ttl=119 time=12.1 ms
64 bytes from 142.251.33.164: icmp_seq=2 ttl=119 time=11.5 ms

--- 142.251.33.164 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 11.493/11.771/12.050/0.278 ms


Reproducible: Always

Actual Results:
I expect ping with a count of 1 packet to work

Expected Results:
Ping with a count of 1 packet does not work, but 2 packets does.

Additional Information:
fping works correctly in the same situation:

# fping -c 1 www.google.com
www.google.com : [0], 64 bytes, 21.8 ms (21.8 avg, 0% loss)

www.google.com : xmt/rcv/%loss = 1/1/0%, min/avg/max = 21.8/21.8/21.8