Re: 2nd Root Server in Europe
Just a note: If anyone tell an address form the network what is the planned location of the new root server, all of us could test the good connectivity. E.g. with traceroute. Regards Gabor
On Tue, 21 Jan 1997, Gabor Kiss wrote:
If anyone tell an address form the network what is the planned location of the new root server, all of us could test the good connectivity. E.g. with traceroute.
Try collector.linx.net = 194.68.130.254 However, quite a few networks have offered to supply transit to the new root name server, so if anything connectivity should be better than what it is now. -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015
Jim Dixon:
Try collector.linx.net = 194.68.130.254
Bingo ! Still the end user's point of view : traceroute to collector.linx.net (194.68.130.253), 30 hops max, 40 byte packets 1 sisint.net.pasteur.fr (157.99.60.1) 1 ms 1 ms 1 ms 2 cerbere.pasteur.fr (157.99.64.1) 2 ms 1 ms 2 ms 3 pasteur-paris.rerif.ft.net (193.49.176.1) 3 ms 3 ms 3 ms 4 stlambert.rerif.ft.net (192.93.50.145) 7 ms 6 ms 6 ms 5 stamand3.renater.ft.net (195.220.180.9) 8 ms 8 ms 8 ms 6 stamand1.renater.ft.net (195.220.180.43) 7 ms 7 ms 7 ms 7 rbs1.renater.ft.net (195.220.180.50) 10 ms 7 ms 8 ms 8 Paris-EBS2.Ebone.net (192.121.156.89) 9 ms 9 ms 12 ms 9 icm-dc-2-S4/0-1984k.icp.net (192.157.65.129) 100 ms 105 ms 91 ms 10 icm-dc-1-F0/0.icp.net (198.67.131.36) 108 ms 97 ms 94 ms 11 icm-mae-e-H1/0-T3.icp.net (198.67.131.9) 303 ms 102 ms 298 ms 12 br2.tco1.alter.net (192.41.177.249) 94 ms 98 ms 99 ms 13 Hssi1-0.CR2.DCA1.Alter.Net (137.39.100.22) 100 ms 121 ms 122 ms 14 Fddi0-0.GW2.DCA1.Alter.Net (137.39.33.132) 92 ms 104 ms 123 ms 15 INSnet-gw1.ALTER.NET (137.39.128.130) 101 ms 94 ms 92 ms 16 s1.lon1gw1.uk.insnet.net (194.177.171.22) 176 ms 172 ms 188 ms 17 atm0-2.lon2gw2.uk.insnet.net (194.177.170.196) 191 ms 187 ms 182 ms 18 collector.linx.net (194.68.130.254) 104 ms 100 ms * So I would really prefer a new root server near Washington. And I'm sure that would also be better to US biz'ness. Free suggestion to european network providers (Ebone and Dante particularly as those 2 are getting a lot of our money, I mean public money) : save the money for a root server and spend it in decent connectivity. (end of stupid-end-user comments). -- Christophe Wolfhugel -+- SIS, Institut Pasteur, Paris Boulot : wolf@pasteur.fr, $HOME : wolf@schnok.fr.net
Try collector.linx.net = 194.68.130.254 Bingo ! Still the end user's point of view : .... 7 rbs1.renater.ft.net (195.220.180.50) 10 ms 7 ms 8 ms 8 Paris-EBS2.Ebone.net (192.121.156.89) 9 ms 9 ms 12 ms 9 icm-dc-2-S4/0-1984k.icp.net (192.157.65.129) 100 ms 105 ms 91 ms 10 icm-dc-1-F0/0.icp.net (198.67.131.36) 108 ms 97 ms 94 ms 11 icm-mae-e-H1/0-T3.icp.net (198.67.131.9) 303 ms 102 ms 298 ms 12 br2.tco1.alter.net (192.41.177.249) 94 ms 98 ms 99 ms 13 Hssi1-0.CR2.DCA1.Alter.Net (137.39.100.22) 100 ms 121 ms 122 ms 14 Fddi0-0.GW2.DCA1.Alter.Net (137.39.33.132) 92 ms 104 ms 123 ms 15 INSnet-gw1.ALTER.NET (137.39.128.130) 101 ms 94 ms 92 ms 16 s1.lon1gw1.uk.insnet.net (194.177.171.22) 176 ms 172 ms 188 ms 17 atm0-2.lon2gw2.uk.insnet.net (194.177.170.196) 191 ms 187 ms 182 ms 18 collector.linx.net (194.68.130.254) 104 ms 100 ms * We're a multi-homed site. The difference in routing between our two providers is small, as shown by these traceroute's, but what it comes down it that they *both* go via the US! Piet ---------------------------------------------------------- 1) Via NLnet: 1 cwi-gw (192.16.184.32) 3 ms 3 ms 3 ms 2 Amsterdam.NL.NL.net (192.16.183.96) 8 ms 5 ms 4 ms 3 Amsterdam4.NL.NL.net (194.178.244.40) 16 ms 31 ms 9 ms 4 Amsterdam2.NL.EU.net (134.222.18.1) 31 ms 251 ms 31 ms 5 * Vienna2.VA.US.EU.net (134.222.228.14) 190 ms 294 ms 6 maeegw1.us.insnet.net (192.41.177.112) 375 ms 302 ms 169 ms 7 s1.lon1gw1.uk.insnet.net (194.177.171.22) 220 ms 208 ms 214 ms 8 atm0-2.lon2gw2.uk.insnet.net (194.177.170.196) 192 ms 189 ms 193 ms 9 collector.linx.net (194.68.130.254) 122 ms * 127 ms 2) Via SURFnet: 1 cwi-gw (192.16.184.32) 3 ms 4 ms 2 ms 2 Amsterdam11.router.surfnet.nl (192.16.183.112) 5 ms 5 ms 5 ms 3 Amsterdam9.router.surfnet.nl (145.41.6.67) 7 ms 5 ms 9 ms 4 New-York2.dante.net (145.41.0.14) 236 ms New-York2.dante.net (145.41.0.2) 196 ms New-York2.dante.net (145.41.0.14) 146 ms 5 f3-1.t32-0.New-York.t3.ans.net (204.149.4.9) 203 ms 209 ms * 6 h9-1.t56-1.Washington-DC.t3.ans.net (140.223.57.29) 240 ms 176 ms 195 ms 7 maeegw1.us.insnet.net (192.41.177.112) 244 ms enss149.t3.ans.net (140.223.57.22) 268 ms 264 ms 8 maeegw1.us.insnet.net (192.41.177.112) 226 ms 193 ms 189 ms 9 atm0-2.lon2gw2.uk.insnet.net (194.177.170.196) 351 ms s1.lon1gw1.uk.insnet.net (194.177.171.22) 349 ms 315 ms 10 collector.linx.net (194.68.130.254) 124 ms * *
Piet Beertema wrote:
Try collector.linx.net = 194.68.130.254 Bingo ! Still the end user's point of view : .... 7 rbs1.renater.ft.net (195.220.180.50) 10 ms 7 ms 8 ms 8 Paris-EBS2.Ebone.net (192.121.156.89) 9 ms 9 ms 12 ms 9 icm-dc-2-S4/0-1984k.icp.net (192.157.65.129) 100 ms 105 ms 91 ms 10 icm-dc-1-F0/0.icp.net (198.67.131.36) 108 ms 97 ms 94 ms 11 icm-mae-e-H1/0-T3.icp.net (198.67.131.9) 303 ms 102 ms 298 ms 12 br2.tco1.alter.net (192.41.177.249) 94 ms 98 ms 99 ms 13 Hssi1-0.CR2.DCA1.Alter.Net (137.39.100.22) 100 ms 121 ms 122 ms 14 Fddi0-0.GW2.DCA1.Alter.Net (137.39.33.132) 92 ms 104 ms 123 ms 15 INSnet-gw1.ALTER.NET (137.39.128.130) 101 ms 94 ms 92 ms 16 s1.lon1gw1.uk.insnet.net (194.177.171.22) 176 ms 172 ms 188 ms 17 atm0-2.lon2gw2.uk.insnet.net (194.177.170.196) 191 ms 187 ms 182 ms 18 collector.linx.net (194.68.130.254) 104 ms 100 ms *
We're a multi-homed site. The difference in routing between our two providers is small, as shown by these traceroute's, but what it comes down it that they *both* go via the US!
Piet
----------------------------------------------------------
1) Via NLnet: 1 cwi-gw (192.16.184.32) 3 ms 3 ms 3 ms 2 Amsterdam.NL.NL.net (192.16.183.96) 8 ms 5 ms 4 ms 3 Amsterdam4.NL.NL.net (194.178.244.40) 16 ms 31 ms 9 ms 4 Amsterdam2.NL.EU.net (134.222.18.1) 31 ms 251 ms 31 ms 5 * Vienna2.VA.US.EU.net (134.222.228.14) 190 ms 294 ms 6 maeegw1.us.insnet.net (192.41.177.112) 375 ms 302 ms 169 ms 7 s1.lon1gw1.uk.insnet.net (194.177.171.22) 220 ms 208 ms 214 ms 8 atm0-2.lon2gw2.uk.insnet.net (194.177.170.196) 192 ms 189 ms 193 ms 9 collector.linx.net (194.68.130.254) 122 ms * 127 ms
2) Via SURFnet: 1 cwi-gw (192.16.184.32) 3 ms 4 ms 2 ms 2 Amsterdam11.router.surfnet.nl (192.16.183.112) 5 ms 5 ms 5 ms 3 Amsterdam9.router.surfnet.nl (145.41.6.67) 7 ms 5 ms 9 ms 4 New-York2.dante.net (145.41.0.14) 236 ms New-York2.dante.net (145.41.0.2) 196 ms New-York2.dante.net (145.41.0.14) 146 ms 5 f3-1.t32-0.New-York.t3.ans.net (204.149.4.9) 203 ms 209 ms * 6 h9-1.t56-1.Washington-DC.t3.ans.net (140.223.57.29) 240 ms 176 ms 195 ms 7 maeegw1.us.insnet.net (192.41.177.112) 244 ms enss149.t3.ans.net (140.223.57.22) 268 ms 264 ms 8 maeegw1.us.insnet.net (192.41.177.112) 226 ms 193 ms 189 ms 9 atm0-2.lon2gw2.uk.insnet.net (194.177.170.196) 351 ms s1.lon1gw1.uk.insnet.net (194.177.171.22) 349 ms 315 ms 10 collector.linx.net (194.68.130.254) 124 ms * *
Folks, the reason for the long path via the US is partly our fault. Sorry. A quick fix on our filters should soon see connections via EBONE and PIPEX directly. Thanks for bringing this to our attention. Regards --Tony
participants (5)
-
Christophe Wolfhugel -
Gabor Kiss -
Jim Dixon -
Piet Beertema -
Tony Barber