US Cable Support > Comcast HSI > [Connectivity] ibone vs cbone

[Connectivity] ibone vs cbone

The 'cbone' is Comcast's internal network. You'll hit that going to another Comcast customer, between Comcast POPs.

Tracing route to te-8-3-ar01.capitolhghts.md.bad.comcast.net [68.86.72.2]
over a maximum of 30 hops:
 
  1     1 ms    <1 ms    <1 ms  172.20.15.1
  2     *        *        *     Request timed out.
  3     9 ms    10 ms    10 ms  ge-1-39-ur01.romeoville.il.chicago.comcast
.net [68.86.118.229]
  4    12 ms    11 ms    12 ms  te-8-2-ar02.elmhurst.il.chicago.comcast.ne
t [68.87.231.90]
  5    14 ms    14 ms    14 ms  te-2-1-ar01.area4.il.chicago.comcast
.net [68.87.230.121]
  6    13 ms    14 ms    14 ms  te-4-1-cr01.chicago.il.cbone.comcast
.net [68.86.72.33]
  7    22 ms    22 ms    22 ms  te-1-1-cr01.cleveland.oh.cbone.comca
st.net [68.86.68.21]
  8    22 ms    30 ms    30 ms  te-1-1-cr02.pittsburgh.pa.cbone.comc
ast.net [68.86.68.118]
  9    42 ms    42 ms    43 ms  te-2-1-cr01.mclean.va.cbone.comcast.
net [68.86.68.126]
 10    50 ms    50 ms    48 ms  te-8-3-ar01.capitolhghts.md.ba
d.comcast.net [68.86.72.2]
 

Tracing route to softlayer.com [66.228.118.53]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms     3 ms  172.20.15.1
  2     *        *        *     Request timed out.
  3    10 ms     8 ms    10 ms  ge-1-39-ur01.romeoville.il.chicago.c
omcast.net [68.86.118.229]
  4    10 ms    10 ms    10 ms  te-8-2-ar02.elmhurst.il.chicag
o.comcast.net [68.87.231.90]
  5    11 ms    11 ms    12 ms  te-2-1-ar01.area4.il.chicago.comcast
.net [68.87.230.121]
  6    16 ms    15 ms    13 ms  68.86.90.49
  7    35 ms    41 ms    38 ms  pos-0-0-0-0-cr01.indianapolis.in.ibo
ne.comcast.net [68.86.85.58]
  8    49 ms    51 ms    48 ms  pos-0-14-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.153]
  9    42 ms    42 ms    50 ms  te1-2.cer02.dal01.dallas-datac
enter.com [75.149.228.34]
 10    50 ms    51 ms    51 ms  po2.dar02.dal01.dallas-datacenter.co
m [66.228.118.207]
 11    49 ms    49 ms    51 ms  po2.slr01.dal01.softlayer.com
[66.228.118.142]
 12    50 ms    50 ms    50 ms  www.softlayer.com [66.228.118.53]
 

I would think cbone is the local backbone, and ibone is national backbone and the gateway to the internet peering points. Thats just pure speculation on my part though

reply to timburke
Timburke, makes sense...so C is basically or Comcast/customer and i is for Internet. It's iteresting how many providers (ThePlanet, SoftLayer, FDCServers) now have Comcast as part of their mix...must be settlement-free or cheap, and probably helps Comcast with transit costs.

OTOH it also means that Comcast can route their network for cost, then flip the blame onto web hosts who haven't participated in their network; unless a target website uses Level3 in a big way, or Comcast's ibone for connection, it gets pretty highly routed. Sometimes it's not so bad; there's peering handoff in Chicago for an East-coast site. However a lot of traffic gets sent down t Santa Teresa, TX, then over to LA, then off the network to elsewhere (GBLX, TWTC, Cogent etc.). Granted, the performance drop is surprisingly low, but you're looking at 25 ms to Dallas/Softlayer on Comcast's network vs. 45 ms to Denver through LA on another network.

A slightly bigger deal: GNAX goes from Denver -> Santa Teresa -> LA -> PCCW/LA -> PCCW/ATL, for a total roundtrip time of ~70ms. Not horrible for the amount of routing around you get, but sub-optimal? Yep.

Even worse, Akamai isn't even directly connected to Comvsdt, so the "CDN" works slower for Comcast customers than people on other networks.

reply to iansltx
Ian, that's correct.

Regarding Comcast not peering with Akamai, iirc they have some peering with Comcast. I'll run some traceroutes when I get home.

Tim

At school right ow but VPN/Telnet'd into my router and here's my trace to www.akamai.com (on their CDN):

traceroute to a152.g.akamai.net (206.57.28.67), 30 hops max, 38 byte packets
1 96.152.60.1 (96.152.60.1) 7.906 ms 7.706 ms 7.195 ms
2 ge-2-5-ur02.wheatridge.co.denver.comcast.net (68.85.220.165) 8.227 ms 8.651 ms 8.518 ms
3 te-9-1-ur01.wheatridge.co.denver.comcast.net (68.86.103.117) 8.111 ms 7.810 ms 7.064 ms
4 te-9-3-ar01.denver.co.denver.comcast.net (68.86.103.17) 9.334 ms 7.617 ms 7.188 ms
5 68.86.91.17 (68.86.91.17) 8.437 ms 10.055 ms 7.594 ms
6 te-0-1-0-1-cr01.santateresa.tx.ibone.comcast.net (68.86.84.70) 22.799 ms 22.164 ms 21.235 ms
7 pos-1-8-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.13) 41.271 ms 44.365 ms 40.595 ms
8 TenGigabitEthernet9-1.ar2.LAX2.gblx.net (64.209.88.29) 39.499 ms 40.346 ms 43.284 ms
9 206.57.28.67 (206.57.28.67) 68.137 ms 73.136 ms 74.228 ms

Whereas on-campus Akamai is one of the peers for our GigaPOP (FRGP) and is thus only a few ms from the network, and is thus extremely fast, provided the network on-campus is working well. Unfortunately right now it's doing horribly so I won't post a traceroute now. Suffice to say there are seven hops to the destination, five of which are involved in getting off my campus network...

Okay, looks like Akamai European ASN actually does connect to one of Comcast's ASNs. But it seems as thoughGlobal Crossing is still the preferred route for Akamai traffic.

Actually, when I was downloading Windows 7 from Akamai several days ago, it looked as though I was getting routed through Tiscali...:/

reply to iansltx
That's kind of odd that you're being routed through Los Angeles. It'd seem like the best location for you to be routed through is Dallas; though I don't see why Comcast wouldn't have bandwidth out of Denver. Try doing a traceroute to www.comcast.net. That's hosted on the Akamai CDN, and does indeed go through Comcast's network as shown here in this traceroute:

Tracing route to a1526.g.akamai.net [96.17.76.16]
over a maximum of 30 hops:
 
  1     3 ms    <1 ms     1 ms  172.20.15.1 
  2     *        *        *     Request timed out.
  3    10 ms    11 ms     9 ms  ge-1-39-ur01.romeoville.il.chicago.comcast.net [68.86.118.229] 
  4    15 ms    11 ms     9 ms  te-8-2-ar02.elmhurst.il.chicago.comcast.net [68.87.231.90] 
  5    13 ms    14 ms    11 ms  te-2-1-ar01.area4.il.chicago.comcast.net [68.87.230.121] 
  6    13 ms    15 ms    13 ms  68.86.90.49 
  7    13 ms    11 ms    14 ms  a96-17-76-16.deploy.akamaitechnologies.com [96.17.76.16] 
 
Trace complete.
 
 

Tracing route to a152.g.akamai.net [96.17.76.25]
over a maximum of 30 hops:
 
  1     1 ms    <1 ms    <1 ms  172.20.15.1 
  2     *        *        *     Request timed out.
  3    12 ms     8 ms    12 ms  ge-1-39-ur01.romeoville.il.chicago.comcast.net [68.86.118.229] 
  4    10 ms     8 ms     9 ms  te-8-2-ar02.elmhurst.il.chicago.comcast.net [68.87.231.90] 
  5    24 ms    14 ms    13 ms  te-2-1-ar01.area4.il.chicago.comcast.net [68.87.230.121] 
  6    17 ms    17 ms    14 ms  pos-0-13-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.53] 
  7    13 ms    14 ms    13 ms  a96-17-76-25.deploy.akamaitechnologies.com [96.17.76.25] 
 
Trace complete.
 

traceroute to 96.17.76.25 (96.17.76.25), 30 hops max, 40 byte packets
 1  v1100.ddr2.Chi3.Servernap.net (69.65.42.62)  1.276 ms  1.228 ms  1.206 ms
 2  p101.csr1.Chi3.Servernap.net (66.252.0.133)  1.207 ms  1.200 ms  1.183 ms
 3  v998.csr2.Chi3.Servernap.net (69.39.239.177)  1.110 ms  1.095 ms  1.088 ms
 4  xe-5-0-0.er1.Chi2.Servernap.net (66.252.0.70)  1.975 ms  1.962 ms  1.944 ms
 5  er1.Chi2-Pccw.br02.Chc01.Servernap.net (66.252.3.130)  1.925 ms  1.912 ms  1.893 ms
 6  68.86.89.57 (68.86.89.57)  2.814 ms  2.942 ms  2.942 ms
 7  a96-17-76-25.deploy.akamaitechnologies.com (96.17.76.25)  2.927 ms  2.908 ms  2.858 ms
 

Hmm, usng 4.2.2.x for my DNS servers as they're faster than Comcast's. wonder if hat's causing routing issues. I'd tend to thin no though...traceroutes to www.comcast.net coming shortly...

reply to timburke
From on-campus (FRGP, peer with Akamai):

Tracing route to a1526.g.akamai.net [192.43.217.245]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms wl-gw.Mines.EDU [138.67.141.254]
2 14 ms 5 ms 5 ms 138.67.63.253
3 7 ms 17 ms 6 ms vermiculite.Mines.EDU [138.67.253.20]
4 7 ms 4 ms 7 ms csm-gw.Mines.EDU [138.67.253.254]
5 20 ms 23 ms 20 ms 138.67.253.10
6 42 ms 18 ms 20 ms frgp-gw-2-vl815.frgp.net [192.43.217.165]
7 23 ms 19 ms 20 ms a192-43-217-245.deploy.akamaitechnologies.com [1
92.43.217.245]

Trace complete.

From home:

traceroute to a1526.g.akamai.net (206.57.28.9), 30 hops max, 38 byte packets
1 96.152.60.1 (96.152.60.1) 7.289 ms 8.328 ms 8.537 ms
2 ge-2-5-ur02.wheatridge.co.denver.comcast.net (68.85.220.165) 7.675 ms 7.880 ms 14.125 ms
3 te-9-1-ur01.wheatridge.co.denver.comcast.net (68.86.103.117) 23.649 ms 10.911 ms 7.914 ms
4 te-9-3-ar01.denver.co.denver.comcast.net (68.86.103.17) 7.984 ms 7.118 ms 11.806 ms
5 68.86.91.17 (68.86.91.17) 7.735 ms 8.015 ms 6.957 ms
6 te-0-1-0-1-cr01.santateresa.tx.ibone.comcast.net (68.86.84.70) 23.818 ms 22.723 ms 21.935 ms
7 pos-1-8-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.13) 44.877 ms 38.736 ms 39.859 ms
8 TenGigabitEthernet8-2.ar2.LAX2.gblx.net (67.17.197.117) 40.397 ms 39.754 ms 40.531 ms
9 206.57.28.9 (206.57.28.9) 52.674 ms 54.067 ms 51.486 ms

Note that traffic gets routed to CHI at times for other stuff, for SingleHop and FDCServers...one over Level3/SCNet, one through Comcast ibone...

traceroute to fdcservers.net (66.90.66.135), 30 hops max, 38 byte packets
1 96.152.60.1 (96.152.60.1) 11.732 ms 3.747 ms 6.340 ms
2 ge-2-5-ur02.wheatridge.co.denver.comcast.net (68.85.220.165) 8.266 ms 6.12 3 ms 11.238 ms
3 te-9-1-ur01.wheatridge.co.denver.comcast.net (68.86.103.117) 6.470 ms 8.33 0 ms 10.217 ms
4 te-9-3-ar01.denver.co.denver.comcast.net (68.86.103.17) 15.912 ms 14.944 m s 11.792 ms
5 68.86.91.17 (68.86.91.17) 8.697 ms 9.814 ms 8.420 ms
6 pos-0-10-0-0-cr01.denver.co.ibone.comcast.net (68.86.86.22) 10.287 ms 13.5 44 ms 11.364 ms
7 68.86.85.245 (68.86.85.245) 34.767 ms 36.032 ms 37.685 ms
8 * 66.90.127.205 (66.90.127.205) 35.927 ms *
9 mail.fdcservers.net (66.90.66.135) 41.130 ms 36.127 ms 35.415 ms

traceroute to singlehop.com (67.212.163.50), 30 hops max, 38 byte packets
1 96.152.60.1 (96.152.60.1) 6.765 ms 6.829 ms 5.713 ms
2 ge-2-5-ur01.wheatridge.co.denver.comcast.net (68.85.220.157) 7.974 ms 8.351 ms 11.308 ms
3 te-9-3-ar01.denver.co.denver.comcast.net (68.86.103.17) 10.569 ms 6.224 ms 8.138 ms
4 68.86.91.17 (68.86.91.17) 7.573 ms 7.960 ms 7.926 ms
5 pos-0-10-0-0-cr01.denver.co.ibone.comcast.net (68.86.86.22) 8.957 ms 7.993 ms 8.185 ms
6 te-4-4.car2.Denver1.Level3.net (4.79.82.57) 9.251 ms 9.184 ms 15.624 ms
7 ae-31-55.ebr1.Denver1.Level3.net (4.68.107.158) 17.111 ms 19.695 ms 17.695 ms
8 ae-1-100.ebr2.Denver1.Level3.net (4.69.132.38) 18.532 ms 19.717 ms 20.081 ms
9 ae-3.ebr1.Chicago2.Level3.net (4.69.132.62) 38.151 ms 37.075 ms 37.637 ms
10 ae-6.ebr1.Chicago1.Level3.net (4.69.140.189) 39.220 ms 39.671 ms 35.725 ms
11 ae-13-55.car3.Chicago1.Level3.net (4.68.101.135) 34.627 ms 34.790 ms 33.936 ms
12 263.xe-0-3-0.cr2.ord1.us.scnet.net (4.71.100.38) 34.892 ms 33.460 ms 40.316 ms
13 v21.ar1.ord1.us.scnet.net (216.246.95.243) 34.684 ms 34.717 ms 35.554 ms
14 as32475.1514.tge4-4.ar1.ord1.us.scnet.net (75.102.19.131) 33.511 ms 34.377 ms 65.565 ms
15 csw00.ord02.singlehop.net (216.104.35.220) 35.028 ms 37.381 ms 36.634 ms
16 201.32.104.216.no-rdns.ord02.singlehop.net (216.104.32.201) 82.504 ms 94.177 ms 43.394 ms
17 web01.singlehop.net (67.212.163.50) 35.315 ms 36.921 ms 36.366 ms

Okay, so it looks like Comcast does have transit in Denver from Level3.

Also, I did a couple nslookups to see if the DNS server is dependent on what CDN IP you get, and it looks like it is. Paste is below:

C:\Documents and Settings\Tim>nslookup
Default Server:  chic-cns.area4.il.chicago.comcast.net
Address:  68.87.72.130
 
> www.comcast.net
Server:  chic-cns.area4.il.chicago.comcast.net
Address:  68.87.72.130
 
Non-authoritative answer:
Name:    a1526.g.akamai.net
Addresses:  96.17.76.96, 96.17.76.131
Aliases:  www.comcast.net, www.comcast.net.edgesuite.net
 
> server 208.67.222.222
Default Server:  resolver1.opendns.com
Address:  208.67.222.222
 
> www.comcast.net
Server:  resolver1.opendns.com
Address:  208.67.222.222
 
Non-authoritative answer:
Name:    a1526.g.akamai.net
Addresses:  128.242.186.224, 128.242.186.200
Aliases:  www.comcast.net, www.comcast.net.edgesuite.net
 
> server 68.94.156.1
Default Server:  dnsr1.sbcglobal.net
Address:  68.94.156.1
 
> www.comcast.net
Server:  dnsr1.sbcglobal.net
Address:  68.94.156.1
 
Non-authoritative answer:
Name:    a1526.g.akamai.net
Addresses:  128.242.191.66, 128.242.191.27
Aliases:  www.comcast.net, www.comcast.net.edgesuite.net
 
> www.comcast.net
Server:  vnsc-pri.sys.gtei.net
Address:  4.2.2.1
 
Non-authoritative answer:
Name:    a1526.g.akamai.net
Addresses:  204.2.228.42, 204.2.228.19
Aliases:  www.comcast.net, www.comcast.net.edgesuite.net
 

reply to iansltx

The cool thing is, the DNS servers I'm using (4.2.2.x) are actually physically close to where I am, maybe 2-4 ms from my cable node. If I go to DoxPara, it lists different IP addresses for my DNS server, so I think it's effectively forwarding to one in Denver, so DNS Akamai geolocation works.

I'm following. Seems like a rather broken system Akamai is using, since DNS servers can cache and do all sorts of odd stuff.

Anyone know what the default DNS servers for Comcast are in the Denver area, and what their location is? On the Level3 DNS servers, it appears as though I'm now being routed to Dallas via Level3 for Akamai stuff. Better...but not perfect if Akamai actually has COmcast-accessible servers in the area.

Hmm, seem to have found dns.cmc.co.denver.comcast.net. Any others? I case you're wondering, yes this did dramatically decrease Akamai pings, but nothing else as far as I can tell. It's not like 3ms of NS resolution is going to make things faster unless the resolution is to a totally different server...

reply to espaeth

OpenDNS Cache Check

traceroute to 74.125.77.103 (74.125.77.103), 30 hops max, 40 byte packets
 1  69.65.40.62 (69.65.40.62)  84.147 ms  84.111 ms  84.107 ms
 2  v998.csr2.Chi3.Servernap.net (69.39.239.177)  0.544 ms  0.550 ms  0.548 ms
 3  xe-5-0-0.er1.Chi2.Servernap.net (66.252.0.70)  1.570 ms  1.572 ms  1.571 ms
 4  56.ge1-12.tsr1.ord1.us.vxl.Servernap.net (66.252.3.142)  1.569 ms  1.565 ms  1.564 ms
 5  * * *
 6  216.239.48.154 (216.239.48.154)  2.031 ms 209.85.250.237 (209.85.250.237)  2.026 ms 216.239.48.154 (216.239.48.154)  2.019 ms
 7  216.239.46.49 (216.239.46.49)  25.420 ms  34.394 ms 216.239.46.15 (216.239.46.15)  23.311 ms
 8  64.233.175.212 (64.233.175.212)  128.316 ms 209.85.255.140 (209.85.255.140)  25.434 ms 209.85.255.138 (209.85.255.138)  25.415 ms
 9  72.14.236.217 (72.14.236.217)  128.788 ms 72.14.236.213 (72.14.236.213)  25.440 ms 216.239.43.123 (216.239.43.123)  139.098 ms
10  66.249.95.130 (66.249.95.130)  130.305 ms  (209.85.130.84)  128.102 ms  128.020 ms
11  209.85.248.80 (209.85.248.80)  142.260 ms 209.85.255.98 (209.85.255.98)  143.405 ms 209.85.248.80 (209.85.248.80)  139.825 ms
12  209.85.248.79 (209.85.248.79)  139.419 ms 72.14.233.114 (72.14.233.114)  310.732 ms  308.542 ms
13  209.85.255.143 (209.85.255.143)  141.862 ms 209.85.255.166 (209.85.255.166)  138.303 ms  139.747 ms
14  209.85.255.98 (209.85.255.98)  145.525 ms 209.85.255.102 (209.85.255.102)  148.485 ms 209.85.255.98 (209.85.255.98)  158.177 ms
15  ew-in-f103.google.com (74.125.77.103)  140.976 ms  139.564 ms  140.525 ms
 

traceroute to 74.125.77.103 (74.125.77.103), 30 hops max, 40 byte packets
 1  v628.core1.mnc1.uk.razorblue.com (86.53.206.129)  1.204 ms  1.485 ms  1.778 ms
 2  razorblue.ifl.telecomplete.net (213.160.121.197)  0.764 ms  0.792 ms  0.263 ms
 3  v700-r3.tcw.telecomplete.net (213.160.116.54)  1.837 ms  1.806 ms  1.777 ms
 4  v951-r1.tch.telecomplete.net (193.0.255.198)  7.943 ms  7.902 ms  7.793 ms
 5  195.66.226.125 (195.66.226.125)  8.674 ms  8.640 ms  8.609 ms
 6  209.85.252.76 (209.85.252.76)  8.075 ms  8.072 ms  8.311 ms
 7  209.85.248.80 (209.85.248.80)  15.745 ms  15.749 ms  15.986 ms
 8  209.85.248.79 (209.85.248.79)  18.307 ms  18.153 ms  18.079 ms
 9  209.85.255.20 (209.85.255.20)  19.824 ms  20.047 ms 209.85.255.143 (209.85.255.143)  19.019 ms
10  209.85.255.110 (209.85.255.110)  27.744 ms 209.85.255.106 (209.85.255.106)  28.130 ms  28.095 ms
11  ew-in-f103.google.com (74.125.77.103)  20.087 ms  20.281 ms  20.350 ms
 

dig +trace www.l.google.com 
 
; <<>> DiG 9.3.3rc2 <<>> +trace www.l.google.com 
; (1 server found)
;; global options:  printcmd
.                       16747   IN      NS      K.ROOT-SERVERS.NET.
.                       16747   IN      NS      H.ROOT-SERVERS.NET.
.                       16747   IN      NS      F.ROOT-SERVERS.NET.
.                       16747   IN      NS      L.ROOT-SERVERS.NET.
.                       16747   IN      NS      E.ROOT-SERVERS.NET.
.                       16747   IN      NS      I.ROOT-SERVERS.NET.
.                       16747   IN      NS      A.ROOT-SERVERS.NET.
.                       16747   IN      NS      D.ROOT-SERVERS.NET.
.                       16747   IN      NS      G.ROOT-SERVERS.NET.
.                       16747   IN      NS      B.ROOT-SERVERS.NET.
.                       16747   IN      NS      M.ROOT-SERVERS.NET.
.                       16747   IN      NS      C.ROOT-SERVERS.NET.
.                       16747   IN      NS      J.ROOT-SERVERS.NET.
;; Received 228 bytes from 4.2.2.2#53(4.2.2.2) in 2 ms
 
com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
;; Received 494 bytes from 193.0.14.129#53(K.ROOT-SERVERS.NET) in 59 ms
 
google.com.             172800  IN      NS      ns1.google.com.
google.com.             172800  IN      NS      ns2.google.com.
google.com.             172800  IN      NS      ns3.google.com.
google.com.             172800  IN      NS      ns4.google.com.
;; Received 170 bytes from 192.5.6.30#53(a.gtld-servers.net) in 107 ms
 
l.google.com.           86400   IN      NS      b.l.google.com.
l.google.com.           86400   IN      NS      f.l.google.com.
l.google.com.           86400   IN      NS      e.l.google.com.
l.google.com.           86400   IN      NS      d.l.google.com.
l.google.com.           86400   IN      NS      c.l.google.com.
l.google.com.           86400   IN      NS      g.l.google.com.
l.google.com.           86400   IN      NS      a.l.google.com.
;; Received 258 bytes from 216.239.32.10#53(ns1.google.com) in 13 ms
 
www.l.google.com.       300     IN      A       74.125.95.104
www.l.google.com.       300     IN      A       74.125.95.147
www.l.google.com.       300     IN      A       74.125.95.103
www.l.google.com.       300     IN      A       74.125.95.99
;; Received 98 bytes from 74.125.45.9#53(b.l.google.com) in 32 ms
 

traceroute to 74.125.95.104 (74.125.95.104), 30 hops max, 40 byte packets
 1  69.65.40.62 (69.65.40.62)  0.572 ms  0.545 ms  0.543 ms
 2  so2-0-0-0.er1.Chi1.Servernap.net (69.39.239.169)  1.592 ms  1.597 ms  1.596 ms
 3  ge-6-20.car1.Chicago1.Level3.net (4.79.65.49)  1.563 ms  1.567 ms  1.573 ms
 4  GOOGLE-INC.car1.Chicago1.Level3.net (4.79.208.18)  1.576 ms  2.036 ms  2.035 ms
 5  209.85.240.158 (209.85.240.158)  2.038 ms  2.027 ms  2.031 ms
 6  72.14.232.141 (72.14.232.141)  12.496 ms  12.648 ms  12.595 ms
 7  209.85.241.35 (209.85.241.35)  12.563 ms  12.549 ms 209.85.241.29 (209.85.241.29)  12.536 ms
 8  209.85.240.45 (209.85.240.45)  19.477 ms  18.963 ms 72.14.239.193 (72.14.239.193)  24.902 ms
 9  iw-in-f104.google.com (74.125.95.104)  12.701 ms  12.491 ms  12.964 ms