I have an issue with traceroutes being very slow. Here are some examples:
time traceroute google.com traceroute to google.com (173.194.35.35), 30 hops max, 60 byte packets 1 194.14.179.252 (194.14.179.252) 0.082 ms 0.025 ms 0.022 ms 2 gw-cdlan-2.prometeus.cdlan.net (217.171.46.253) 0.347 ms 0.409 ms 0.454 ms 3 ibgp-gw-core-a.cdlan.net (217.171.32.129) 0.712 ms 0.783 ms 0.850 ms 4 google.mix-it.net (217.29.66.96) 0.243 ms 0.278 ms 0.226 ms 5 209.85.249.54 (209.85.249.54) 0.352 ms 0.280 ms 0.258 ms 6 209.85.241.67 (209.85.241.67) 0.598 ms 1.229 ms 1.261 ms 7 mil01s17-in-f3.1e100.net (173.194.35.35) 0.389 ms 0.385 ms 0.498 ms real 0m15.567s
time traceroute -n google.com traceroute to google.com (173.194.35.35), 30 hops max, 60 byte packets 1 194.14.179.252 0.041 ms 0.018 ms 0.015 ms 2 217.171.46.253 0.405 ms 0.454 ms 0.514 ms 3 217.171.32.129 0.365 ms 0.450 ms 0.684 ms 4 217.29.66.96 0.237 ms 0.238 ms 0.252 ms 5 209.85.249.54 0.302 ms 0.366 ms 0.273 ms 6 209.85.241.67 0.868 ms 0.966 ms 1.063 ms 7 173.194.35.35 0.297 ms 0.269 ms 0.307 ms real 0m0.005s
time traceroute6 google.com traceroute to google.com (2a00:1450:4002:802::1000) from xxx, 30 hops max, 16 byte packets 1 2a00:dcc0:eda:89::252 (2a00:dcc0:eda:89::252) 0.22 ms 0.367 ms 0.137 ms 2 gw6.prometeus.net (2a00:dcc0:eda:2::1) 0.467 ms 0.431 ms 0.411 ms 3 2001:b60:0:c100::1 (2001:b60:0:c100::1) 0.938 ms 0.953 ms 0.851 ms 4 google-v6.mix-it.net (2001:7f8:b:100:1d1:a5d1:5169:96) 5.072 ms 29.613 ms 29.646 ms 5 2001:4860::1:0:458d (2001:4860::1:0:458d) 2.155 ms 2.106 ms 1.992 ms 6 2001:4860:0:1::4c7 (2001:4860:0:1::4c7) 1.196 ms 1.35 ms 1.146 ms 7 2a00:1450:8000:17::8 (2a00:1450:8000:17::8) 0.94 ms 1.064 ms 1 ms real 0m0.912s
(I've also tested this with other domains)
As you can see the bottleneck seems to be the reverse DNS lookups of IPv4 addresses. Does anyone know how to fix this?