I've noticed when pinging an IPv6 host the first ping response will be several hundred ms higher then subsequent responses. It seems to happen more often when pinging via hostname which I figured was just the time it took for a DNS resolve, yet it does happen sometimes on just pinging an IPv6 address.
Any clues to what might be causing this?
IPv4 works fine, most systems are running KVM/XEN but it happens on my OpenVZ as well. It happens on different boxes with different networks, only thing in common is they all run Debian.
ping6 2a00:dcc0:eda:88:245:71:2da2:12d5 PING 2a00:dcc0:eda:88:245:71:2da2:12d5(2a00:dcc0:eda:88:245:71:2da2:12d5) 56 data bytes 64 bytes from 2a00:dcc0:eda:88:245:71:2da2:12d5: icmp_seq=1 ttl=49 time=707 ms 64 bytes from 2a00:dcc0:eda:88:245:71:2da2:12d5: icmp_seq=2 ttl=49 time=168 ms 64 bytes from 2a00:dcc0:eda:88:245:71:2da2:12d5: icmp_seq=3 ttl=49 time=168 ms ping6 italy.sonicboxes.net PING italy.sonicboxes.net(italy.sonicboxes.net) 56 data bytes 64 bytes from italy.sonicboxes.net: icmp_seq=1 ttl=53 time=552 ms 64 bytes from italy.sonicboxes.net: icmp_seq=2 ttl=53 time=154 ms 64 bytes from italy.sonicboxes.net: icmp_seq=3 ttl=53 time=154 ms
Try any of my looking glass severs (aside from buffalo) if you want to see for yourself.
Germany: PING google.com(muc03s02-in-x05.1e100.net) 56 data bytes 64 bytes from muc03s02-in-x05.1e100.net: icmp_seq=1 ttl=56 time=73.4 ms 64 bytes from muc03s02-in-x05.1e100.net: icmp_seq=2 ttl=56 time=7.68 ms 64 bytes from muc03s02-in-x05.1e100.net: icmp_seq=3 ttl=56 time=7.88 ms
I'm hoping one of our networking guru's has an answer.