Re: ip list is always handy

From: Martin (nospam_at_where-ever.com)
Date: 11/25/03 

Date: Tue, 25 Nov 2003 22:46:42 GMT

> Is it just the name lookup, or can you get there using IP address? How
> far does a traceroute get you?
>
> Here's some DNS entries
> www.zonelabs.com. 300 IN A 208.185.174.44
> lockup.zonelabs.com. 300 IN A 208.185.174.60

Can't reach the sites on ip-address.(putted the DN & Ip into my hostfile)
.
Traceroute:
traceroute to 208.185.174.44 (208.185.174.44), 30 hops max, 38 byte packets
 1 x.x.x.x (x.x.x.x) 0.312 ms 0.249 ms 0.229 ms
 2 x.x.x.x (x.x.x.x) 20.509 ms 18.537 ms 30.793 ms
 3 Gig6-0.zp00rt01.brain.upc.nl (212.142.23.193) 28.287 ms 18.581 ms
9.511 ms
 4 srp13-0.ah00rt01.brain.upc.nl (212.142.32.137) 20.793 ms 28.906 ms
27.643 ms
 5 srp8-0.ah00rt01.brain.upc.nl (212.142.32.49) 23.102 ms 18.622 ms
23.620 ms
 6 srp0-0.am00rt05.brain.upc.nl (212.142.32.43) 24.279 ms 21.938 ms
15.692 ms
 7 nl-ams01a-ra1-so-0-0-2.aorta.net (213.46.161.45) 20.150 ms 31.142 ms
36.344 ms
 8 nl-ams01a-rd1-pos-0-3.aorta.net (213.46.161.189) 21.448 ms 21.406 ms
18.709 ms
 9 213.46.161.141 (213.46.161.141) 25.523 ms 23.338 ms 24.119 ms
10 pos0-1.mpr1.ams1.nl.mfnx.net (62.4.95.241) 28.709 ms 20.686 ms 19.908
ms
11 208.184.231.254 (208.184.231.254) 30.457 ms 28.107 ms 18.229 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
...
...

traceroute to 208.185.174.60 (208.185.174.60), 30 hops max, 38 byte packets
 1 x.x.x.x (x.x.x.x) 0.346 ms 0.267 ms 0.227 ms
 2 x.x.x.x (x.x.x.x) 34.969 ms 21.111 ms 20.382 ms
 3 Gig6-0.zp00rt01.brain.upc.nl (212.142.23.193) 19.618 ms 33.236 ms
18.952 ms
 4 srp13-0.ah00rt02.brain.upc.nl (212.142.32.138) 32.537 ms 15.768 ms
22.085 ms
 5 srp8-0.ah00rt01.brain.upc.nl (212.142.32.49) 15.662 ms 19.152 ms
18.258 ms
 6 srp0-0.am00rt05.brain.upc.nl (212.142.32.43) 18.947 ms 133.440 ms
31.906 ms
 7 nl-ams01a-ra1-so-0-0-2.aorta.net (213.46.161.45) 27.355 ms 23.743 ms
15.579 ms
 8 nl-ams01a-rd1-pos-0-3.aorta.net (213.46.161.189) 18.006 ms 19.766 ms
21.261 ms
 9 213.46.161.141 (213.46.161.141) 26.285 ms 23.005 ms 19.743 ms
10 pos0-1.mpr1.ams1.nl.mfnx.net (62.4.95.241) 18.537 ms 24.251 ms 19.489
ms
11 208.184.231.254 (208.184.231.254) 35.220 ms 26.373 ms 18.651 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
...
...

That's about it. trace just keeps going but with no end to it.

-Martin

Relevant Pages

  • Re: IP->DNS Lookup Incorrect, Inconsistent... just plain frustrating!
    ... I changed the DNS entries to point ... >could be causing me to continue to lookup to old IP address instead of ... >point everything started pointing to the old IP address again. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: IP->DNS Lookup Incorrect, Inconsistent... just plain frustrating!
    ... I changed the DNS entries to point ... >could be causing me to continue to lookup to old IP address instead of ... >point everything started pointing to the old IP address again. ...
    (microsoft.public.windowsxp.network_web)
  • Re: traceroute, now what?
    ... I think you're looking for "whois". ... to lookup by IP address, or once you do an nslookup, try ... I've done a traceroute on the ... I thought it had something to do with a DNS lookup ...
    (comp.os.linux.security)
  • Re: ip list is always handy
    ... Tracing route to 208.185.174.44 over a maximum of 30 hops ... >> Is it just the name lookup, or can you get there using IP address? ... >> far does a traceroute get you? ...
    (comp.security.firewalls)
  • Re: ISP from the number
    ... Yes, try whois, traceroute or dns. ... Also an lookup of the oenwer of the AS might help. ...
    (comp.security.misc)