On Tue, Sep 21, 2004 at 09:46:10AM -0500, Kent West wrote: > I just tried it from my Debian box at the office; took about 51 seconds, > 50 of which were spent "resolving www.nytimes.com". A traceroute gets > about 13 hops down the route and then hits a major snag just after > ge-1-2.a00.nycmny01.us.da.verio.net, getting nothing but three *'s on > each hop thereafter. (I'm too traceroute-illiterate to know what this > means, but I'm pretty sure it's not supposed to do that).
It means the ttl-exceeded message traceroute was expecting back from the packet it sent never arrived, usually it's due to firewalls blocking outbound icmp. If you want to know how long it takes to resolve a hosts name, dig <hostname> is the best way, it informs you how long the transaction took in the output. -- _ _ _ _ _ _ _ _ _ _ _ _ _ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ ( t | i | m | @ | i | t | . | k | p | t | . | c | c ) \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ GPG key fingerprint = 1DEE CD9B 4808 F608 FBBF DC21 2807 D7D3 09CA 85BF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
