traceroute vs ping -R

[mike miskulin]

Hello -

Trying to get my head around something.  Below are output of ping and
traceroute to the same host.  I have used ping -R to record the route. I
do understand that ping -R will only give a limited number of hops (9?),
that is not the question.   

My question is - why is the output of ping -R so different than
traceroute?  What happened to the routes listed in the ping -R?

Two examples listed below

ping -R -c 1 www.bnl.gov
PING cache3.bnl.gov (130.199.3.21): 56 data bytes
64 bytes from 130.199.3.21: icmp_seq=0 ttl=55 time=164.759 ms
RR:     L1.NYCMNY-VFTTP-171.verizon-gni.net (130.81.234.129)
        B400.NYCMNY-LCR-21.verizon-gni.net (130.81.199.163)
        lo0-0.NY325-BB-RTR1.verizon-gni.net (130.81.254.41)
        0.lo0.BR1.NYC1.ALTER.NET (137.39.3.13)
        lo-0.edge2.NewYork2.Level3.net (4.68.185.31)
        vlan723.car4.NewYork1.Level3.net (4.28.72.233)
        aofacr5-ip-b-bnlmr2.es.net (134.55.220.73)
        bnl-mr2.es.net (134.55.200.102)
        cm0515-901.bnl.gov (130.199.3.124)

--- cache3.bnl.gov ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 164.759/164.759/164.759/0.000 ms

traceroute -n www.bnl.gov
traceroute to cache3.bnl.gov (130.199.3.21), 64 hops max, 40 byte packets
 1  4.69.134.74  22.045 ms
    4.69.134.66  22.459 ms
    4.69.148.42  22.432 ms
 2  4.69.148.42  19.945 ms
    4.69.134.78  24.988 ms
    4.69.134.70  27.494 ms
 3  4.69.134.78  17.411 ms
    4.69.148.38  29.987 ms
    4.69.134.74  22.518 ms
 4  4.69.148.38  29.938 ms
    4.69.134.66  27.454 ms
    4.69.148.34  22.485 ms
 5  4.69.134.70  19.964 ms  19.969 ms
    4.69.134.66  22.477 ms
 6  4.69.134.74  29.943 ms
    4.69.134.70  19.972 ms
    4.69.148.46  19.964 ms
 7  4.69.134.70  19.963 ms
    4.69.134.66  32.516 ms  22.424 ms
 8  4.69.148.38  22.527 ms
    4.69.134.74  29.960 ms
    4.69.148.38  22.460 ms
 9  4.69.155.198  97.481 ms
    4.69.155.70  42.435 ms  157.520 ms
10  4.28.72.234  14.955 ms  19.949 ms  22.438 ms
11  134.55.221.138  27.508 ms  42.420 ms
    134.55.220.74  19.993 ms
12  198.124.216.190  27.503 ms  19.970 ms  19.995 ms
13  130.199.3.21  19.963 ms !Z  19.995 ms !Z  19.964 ms !Z



ping -R -c 1 www.erh.noaa.gov
PING a1856.g.akamai.net (23.66.230.18): 56 data bytes
64 bytes from 23.66.230.18: icmp_seq=0 ttl=62 time=22.280 ms
RR:     L1.NYCMNY-VFTTP-171.verizon-gni.net (130.81.234.129)
        B300.NYCMNY-LCR-21.verizon-gni.net (130.81.199.155)
        0.lo0.GW9.IAD8.ALTER.NET (137.39.7.220)
        a23-66-230-1.deploy.static.akamaitechnologies.com (23.66.230.1)
        a23-66-230-18.deploy.static.akamaitechnologies.com (23.66.230.18)
        a23-66-230-18.deploy.static.akamaitechnologies.com (23.66.230.18)
        akamai.customer.alter.net (152.179.50.174)
        0.lo0.GW9.IAD8.ALTER.NET (137.39.7.220)
        L100.NYCMNY-VFTTP-59.verizon-gni.net (72.89.90.1)

--- a1856.g.akamai.net ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.280/22.280/22.280/0.000 ms


 traceroute www.erh.noaa.gov
traceroute: Warning: www.erh.noaa.gov has multiple addresses; using 23.67.244.107
traceroute to a1856.g.akamai.net (23.67.244.107), 64 hops max, 40 byte packets
 1  a23-67-244-107.deploy.static.akamaitechnologies.com (23.67.244.107)  16.884 ms  17.379 ms  17.497 ms