/Users/vick4522 ==> traceroute vickistan.com
traceroute to vickistan.com (108.166.91.129), 64 hops max, 52 byte packets
1 72.32.115.226 (72.32.115.226) 172.771 ms 83.839 ms 89.278 ms
2 67.192.56.50 (67.192.56.50) 95.320 ms 95.043 ms 92.113 ms
3 coreb.dfw1.rackspace.net (74.205.108.26) 94.737 ms
corea.dfw1.rackspace.net (74.205.108.10) 109.197 ms
coreb.dfw1.rackspace.net (74.205.108.26) 116.713 ms
4 core3.dfw1.rackspace.net (74.205.108.7) 117.443 ms
core3.dfw1.rackspace.net (74.205.108.23) 121.774 ms
core3.dfw1.rackspace.net (74.205.108.7) 134.359 ms
5 108-166-91-129.static.cloud-ips.com (108.166.91.129) 136.568 ms !Z 141.209 ms !Z 149.034 ms !Z
Since Linux uses UDP for trace-routes, this can originate from a –reject-with icmp-host-prohibited rule in the destination host’s firewall. Some Linux distros have this as a default configuration. To fix this you need to reply with –reject-with icmp-port-unreachable on UDP ports 33434 through 33534 instead.
If a packet is not acknowledged within the expected timeout, an asterisk is displayed.
