North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: updated root hints file

  • From: Stephane Bortzmeyer
  • Date: Fri Jan 30 07:36:59 2004

On Wed, Jan 28, 2004 at 09:19:43PM -0500,
 Coppola, Brian <[email protected]> wrote 
 a message of 22 lines which said:

> In preparation for tomorrow morning's B-root IP change from 128.9.0.107 to
> 192.228.79.201 

I notice trouble to reach the new server from many places.

Here a machine connected by Global Crossing:

master:~ % dig @192.228.79.201 SOA .  

; <<>> DiG 9.2.1 <<>> @192.228.79.201 SOA .
;; global options:  printcmd
;; connection timed out; no servers could be reached

>From other places, it works. I cannot find a common pattern.

When it fails, the traceroute looks like (here from 146.82.138.7):

master:~ %  traceroute 192.228.79.201
traceroute to 192.228.79.201 (192.228.79.201), 30 hops max, 38 byte packets
 1  mauser.brainfood.com (146.82.138.1)  0.232 ms  0.165 ms  0.121 ms
 2  146.82.136.53 (146.82.136.53)  0.514 ms  0.478 ms  0.450 ms
 3  146.82.136.9 (146.82.136.9)  0.422 ms  0.388 ms  0.368 ms
 4  332.ge12-0.mpr1.dfw2.us.above.net (209.133.66.58)  0.828 ms  0.857 ms  1.162 ms
 5  so-3-0-0.cr2.dfw2.us.above.net (216.200.127.217)  1.001 ms  0.990 ms  0.943 ms
 6  pos3-0.er1.atl4.us.above.net (216.200.127.225)  18.004 ms  17.945 ms  17.921 ms
 7  pos14-0.pr1.atl4.us.above.net (64.125.30.242)  18.015 ms  17.985 ms  17.954 ms
 8  so-1-3.hsa2.Atlanta1.Level3.net (209.0.227.161)  18.123 ms  18.006 ms  17.997 ms
 9  ge-6-2-1.bbr1.Atlanta1.Level3.net (64.159.3.73)  18.341 ms  18.142 ms  18.224 ms
10  so-3-0-0.mpls1.Tustin1.Level3.net (209.247.8.121)  53.037 ms  52.893 ms  53.471 ms
11  so-9-0.hsa1.Tustin1.Level3.net (209.244.27.174)  52.944 ms so-10-0.hsa1.Tustin1.Level3.net (209.244.27.154)  52.913 ms so-9-0.hsa1.Tustin1.Level3.net (209.244.27.174)  52.884 ms
12  * * *
13  130.152.181.66 (130.152.181.66)  63.972 ms  65.680 ms  63.889 ms
14  * * *
15  * * *

When it succeeds, I get (here from 66.93.172.18):

voltaire:~ % traceroute 192.228.79.201
traceroute to 192.228.79.201 (192.228.79.201), 30 hops max, 38 byte packets
 1  dsl093-172-001.pit1.dsl.speakeasy.net (66.93.172.1)  386.978 ms  59.405 ms  125.981 ms
 2  border1.g4-3.speakeasy-40.wdc.pnap.net (63.251.83.187)  164.026 ms  306.738 ms  548.859 ms
 3  core2.ge3-1-bbnet2.wdc002.pnap.net (216.52.127.72)  33.304 ms  242.007 ms  184.611 ms
 4  ge-5-1-181.ipcolo1.Washington1.Level3.net (63.210.59.237)  78.556 ms  464.994 ms  357.447 ms
 5  ae-0-56.bbr2.Washington1.Level3.net (64.159.18.162)  252.687 ms  518.383 ms  402.284 ms
 6  so-3-0-0.mpls1.Tustin1.Level3.net (209.247.8.121)  631.193 ms  485.623 ms  500.692 ms
 7  so-9-0.hsa1.Tustin1.Level3.net (209.244.27.174)  460.843 ms  259.303 ms  339.851 ms
 8  67.30.130.66 (67.30.130.66)  305.469 ms  312.075 ms  341.656 ms
 9  130.152.181.66 (130.152.181.66)  373.986 ms  499.069 ms  518.800 ms
10  b.root-servers.net (192.228.79.201)  461.216 ms  448.530 ms  488.763 ms

So, apparently, 67.30.130.66 does not know how to reply to many
places.

IP addresses which have the problem: 192.134.4.152, 146.82.138.7,
194.117.194.82, 62.23.209.250.