Sometimes out of curiosity, I will check to see what my IP address is and where it is located since I have a dynamic IP address. If I am in Dallas and it says my IP address is located in Ft. Worth, for example, what does that mean? That the SERVER is located in Ft. Worth or what?
IP Address
- Thread starter Footpounds
- Start date
- Status
It just looks up who owns it, I think.
http://ws.arin.net/whois/?queryinput=! NET-12-46-91-0-1
http://ws.arin.net/whois/?queryinput=! NET-12-46-91-0-1
Last edited by a moderator:
Hmmm just curious....sometimes mine says 'Ft. Worth', sometimes 'Dallas'...I've even had one in 'Columbus' and once had one in 'New York'. ?????
If you have a big ISP maybe they are mixing them up? I know my Dad has Cox in Vegas and the IP has a reverse DNS ending in lv.lv.cox.net. Pretty obvious where that is.
The more accurate way to determine where you are at is using something like trace route (tracert in windows). use that with a well known destination (i.e. www.bobistheoilguy.com) and see what path does the data travel through, then you'll see where are you from.
Originally Posted By: PandaBear
The more accurate way to determine where you are at is using something like trace route (tracert in windows). use that with a well known destination (i.e. www.bobistheoilguy.com) and see what path does the data travel through, then you'll see where are you from.
Yes, this does work, often times the routers will have reverse DNS that gives away the location.
Code:
colton@sarah ~ $ traceroute www.bobistheoilguy.com
traceroute to www.bobistheoilguy.com (205.243.146.146), 30 hops max, 60 byte packets
1 10.204.0.1 (10.204.0.1) 77.595 ms 77.527 ms 77.501 ms
2 host-64-234-41-1.nctv.com (64.234.41.1) 77.482 ms 77.471 ms 77.460 ms
3 12.117.202.33 (12.117.202.33) 86.012 ms 86.030 ms 86.629 ms
4 cr2.st6wa.ip.att.net (12.122.146.214) 86.624 ms 86.621 ms 86.583 ms
5 12.122.146.173 (12.122.146.173) 78.625 ms 94.123 ms 94.117 ms
6 192.205.33.122 (192.205.33.122) 94.105 ms 70.328 ms 73.818 ms
7 0.so-7-3-0.XT1.SEA1.ALTER.NET (152.63.105.18) 73.801 ms 73.804 ms 73.792 ms
8 0.ge-5-0-0.XT1.CHI2.ALTER.NET (152.63.0.89) 124.231 ms 82.840 ms 82.795 ms
9 POS6-0.GW3.CHI2.ALTER.NET (152.63.64.161) 82.695 ms 82.725 ms 98.526 ms
10 xnet-gw.customer.alter.net (65.207.238.62) 98.529 ms 98.532 ms 98.521 ms
11 www.bobistheoilguy.com (205.243.146.146) 98.510 ms 98.501 ms 85.756 ms
The first one is internal to the cable network, the second is their local router. Then it ends up in seattle for a couple hops before jumping to what appears to be chicago where it hits the router for the data center and finally BITOG.
The more accurate way to determine where you are at is using something like trace route (tracert in windows). use that with a well known destination (i.e. www.bobistheoilguy.com) and see what path does the data travel through, then you'll see where are you from.
Yes, this does work, often times the routers will have reverse DNS that gives away the location.
Code:
colton@sarah ~ $ traceroute www.bobistheoilguy.com
traceroute to www.bobistheoilguy.com (205.243.146.146), 30 hops max, 60 byte packets
1 10.204.0.1 (10.204.0.1) 77.595 ms 77.527 ms 77.501 ms
2 host-64-234-41-1.nctv.com (64.234.41.1) 77.482 ms 77.471 ms 77.460 ms
3 12.117.202.33 (12.117.202.33) 86.012 ms 86.030 ms 86.629 ms
4 cr2.st6wa.ip.att.net (12.122.146.214) 86.624 ms 86.621 ms 86.583 ms
5 12.122.146.173 (12.122.146.173) 78.625 ms 94.123 ms 94.117 ms
6 192.205.33.122 (192.205.33.122) 94.105 ms 70.328 ms 73.818 ms
7 0.so-7-3-0.XT1.SEA1.ALTER.NET (152.63.105.18) 73.801 ms 73.804 ms 73.792 ms
8 0.ge-5-0-0.XT1.CHI2.ALTER.NET (152.63.0.89) 124.231 ms 82.840 ms 82.795 ms
9 POS6-0.GW3.CHI2.ALTER.NET (152.63.64.161) 82.695 ms 82.725 ms 98.526 ms
10 xnet-gw.customer.alter.net (65.207.238.62) 98.529 ms 98.532 ms 98.521 ms
11 www.bobistheoilguy.com (205.243.146.146) 98.510 ms 98.501 ms 85.756 ms
The first one is internal to the cable network, the second is their local router. Then it ends up in seattle for a couple hops before jumping to what appears to be chicago where it hits the router for the data center and finally BITOG.
Code:
C:\>tracert bobistheoilguy.com
Tracing route to bobistheoilguy.com [205.243.146.146]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 10.1.0.1
2 50 ms 37 ms 35 ms 10.33.1.1
3 38 ms 5 ms 42 ms so-2-3-0-0.DFW01-CORE-RTR1.verizon-gni.net [130.81.16.72]
4 38 ms 38 ms 61 ms as0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.20.6
0]
5 56 ms 51 ms 64ms 0.so-1-3-0.XT3.DFW9.ALTER.NET [152.63.0.25]
6 81 ms 85 ms 108 ms 0.ge-2-2-0.XT1.CHI2.ALTER.NET [152.63.0.105]
7 64 ms 61 ms 60 ms POS6-0.GW3.CHI2.ALTER.NET [152.63.64.161]
8 119 ms 271 ms 342 ms xnet-gw.customer.alter.net [65.207.238.62]
9 69 ms 63 ms 125 ms www.bobistheoilguy.com [205.243.146.146]
This is what it looks like coming from the Houston area. I go up through DFW Verizon to chicago, just as Onmo' shows in his 7th step. This may help you conceptualize how we get where we go on the network.
C:\>tracert bobistheoilguy.com
Tracing route to bobistheoilguy.com [205.243.146.146]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 10.1.0.1
2 50 ms 37 ms 35 ms 10.33.1.1
3 38 ms 5 ms 42 ms so-2-3-0-0.DFW01-CORE-RTR1.verizon-gni.net [130.81.16.72]
4 38 ms 38 ms 61 ms as0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.20.6
0]
5 56 ms 51 ms 64ms 0.so-1-3-0.XT3.DFW9.ALTER.NET [152.63.0.25]
6 81 ms 85 ms 108 ms 0.ge-2-2-0.XT1.CHI2.ALTER.NET [152.63.0.105]
7 64 ms 61 ms 60 ms POS6-0.GW3.CHI2.ALTER.NET [152.63.64.161]
8 119 ms 271 ms 342 ms xnet-gw.customer.alter.net [65.207.238.62]
9 69 ms 63 ms 125 ms www.bobistheoilguy.com [205.243.146.146]
This is what it looks like coming from the Houston area. I go up through DFW Verizon to chicago, just as Onmo' shows in his 7th step. This may help you conceptualize how we get where we go on the network.
Quote:
traceroute bobistheoilguy.com
traceroute to bobistheoilguy.com (205.243.146.146), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2.285 ms 1.531 ms 1.495 ms
2 10.88.0.1 (10.88.0.1) 11.763 ms 10.451 ms 13.129 ms
3 d226-4-209.home.cgocable.net (24.226.4.209) 14.119 ms 22.012 ms 27.737 ms
4 102-0-226-24.cgocable.net (24.226.0.102) 15.949 ms 17.854 ms 17.084 ms
5 te3-5.1212.ccr02.yyz02.atlas.cogentco.com (38.112.240.137) 18.430 ms 16.305 ms 15.374 ms
6 te7-8.ccr02.ord01.atlas.cogentco.com (154.54.7.73) 34.739 ms
te2-2.ccr02.ord01.atlas.cogentco.com (154.54.7.169) 42.199 ms 37.794 ms
7 vl3498.ccr02.ord03.atlas.cogentco.com (154.54.5.2) 34.307 ms
te1-1.ccr02.ord03.atlas.cogentco.com (154.54.29.22) 41.419 ms
vl3491.ccr02.ord03.atlas.cogentco.com (154.54.6.210) 39.094 ms
8 0.ge-1-0-0.br1.chi13.alter.net (204.255.168.61) 32.187 ms 31.629 ms 35.000 ms
9 0.ge-5-3-0.xl4.chi13.alter.net (152.63.65.45) 32.298 ms 34.941 ms 32.656 ms
10 0.so-5-2-0.xt2.chi2.alter.net (152.63.64.13) 32.915 ms 35.813 ms 34.229 ms
11 pos7-0.gw3.chi2.alter.net (152.63.64.173) 34.499 ms 31.788 ms 30.425 ms
12 xnet-gw.customer.alter.net (65.207.238.62) 42.140 ms 45.257 ms 34.836 ms
13 www.bobistheoilguy.com (205.243.146.146) 32.878 ms 38.819 ms 49.600 ms
Here's mine; from Windsor, Ontario, Canada.
Why do I think this thread will quickly become 50 pages long, like when *everyone* had to post their speedtest.net results!
traceroute bobistheoilguy.com
traceroute to bobistheoilguy.com (205.243.146.146), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2.285 ms 1.531 ms 1.495 ms
2 10.88.0.1 (10.88.0.1) 11.763 ms 10.451 ms 13.129 ms
3 d226-4-209.home.cgocable.net (24.226.4.209) 14.119 ms 22.012 ms 27.737 ms
4 102-0-226-24.cgocable.net (24.226.0.102) 15.949 ms 17.854 ms 17.084 ms
5 te3-5.1212.ccr02.yyz02.atlas.cogentco.com (38.112.240.137) 18.430 ms 16.305 ms 15.374 ms
6 te7-8.ccr02.ord01.atlas.cogentco.com (154.54.7.73) 34.739 ms
te2-2.ccr02.ord01.atlas.cogentco.com (154.54.7.169) 42.199 ms 37.794 ms
7 vl3498.ccr02.ord03.atlas.cogentco.com (154.54.5.2) 34.307 ms
te1-1.ccr02.ord03.atlas.cogentco.com (154.54.29.22) 41.419 ms
vl3491.ccr02.ord03.atlas.cogentco.com (154.54.6.210) 39.094 ms
8 0.ge-1-0-0.br1.chi13.alter.net (204.255.168.61) 32.187 ms 31.629 ms 35.000 ms
9 0.ge-5-3-0.xl4.chi13.alter.net (152.63.65.45) 32.298 ms 34.941 ms 32.656 ms
10 0.so-5-2-0.xt2.chi2.alter.net (152.63.64.13) 32.915 ms 35.813 ms 34.229 ms
11 pos7-0.gw3.chi2.alter.net (152.63.64.173) 34.499 ms 31.788 ms 30.425 ms
12 xnet-gw.customer.alter.net (65.207.238.62) 42.140 ms 45.257 ms 34.836 ms
13 www.bobistheoilguy.com (205.243.146.146) 32.878 ms 38.819 ms 49.600 ms
Here's mine; from Windsor, Ontario, Canada.
Why do I think this thread will quickly become 50 pages long, like when *everyone* had to post their speedtest.net results!
- Status
Similar threads
