Traceroute Vs. nmap --traceroute discrepency

Discussion in 'other software & services' started by Searching_ _ _, Jan 20, 2010.

Thread Status:
Not open for further replies.
  1. Searching_ _ _

    Searching_ _ _ Registered Member

    Joined:
    Jan 2, 2008
    Posts:
    1,988
    Location:
    iAnywhere
    Running traceroute from a console for any url, the trace doesn't complete, giving asterisks for the last few hops.
    Running the same url with nmap --traceroute it is able to complete the trace.

    It always seems to have a problem when it reaches MCI , Splice Technologies in VA.
    It also appears that certain url's always go through this particular hop.

    Should these two programs be consistent in reporting results?

    Code:
    # traceroute www.google.com
    traceroute to www.google.com (208.69.32.231), 30 hops max, 60 byte packets
    
     8  65.222.158.82 (65.222.158.82)  17.353 ms  17.433 ms  17.400 ms
     9  * * *
    
    Code:
    # nmap --traceroute www.google.com
    
    Warning: Hostname www.google.com resolves to 2 IPs. Using 208.69.32.230.
    Interesting ports on google.navigation.opendns.com (208.69.32.230):
    
    TRACEROUTE 
    HOP RTT   ADDRESS
    
    9   17.20 POS6-0.GW4.IAD8.ALTER.NET (152.63.41.29)
    10  14.49 65.222.158.82
    11  16.68 google.navigation.opendns.com (208.69.32.230)
    
     
  2. nineine

    nineine Registered Member

    Joined:
    Sep 13, 2009
    Posts:
    140
    Why does google.navigation.opendns.com show the google search homepage? Does google own opendns? I thought google has its own googledns.
     
  3. whitedragon551

    whitedragon551 Registered Member

    Joined:
    Sep 30, 2008
    Posts:
    3,189
    Location:
    USA
    Id go with nmap over Traceroute. Much more accurate.
     
Loading...
Thread Status:
Not open for further replies.