[75588] in North American Network Operators' Group
Re: anycast roots
daemon@ATHENA.MIT.EDU (Matt Larson)
Wed Nov 17 14:34:20 2004
Date: Wed, 17 Nov 2004 14:33:42 -0500
From: Matt Larson <mlarson@verisign.com>
To: "Elmar K. Bins" <elmi@4ever.de>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, nanog@merit.edu
In-Reply-To: <20041117133724.GM34085@new.detebe.org>
Errors-To: owner-nanog-outgoing@merit.edu
On Wed, 17 Nov 2004, Elmar K. Bins wrote:
>
> bortzmeyer@nic.fr (Stephane Bortzmeyer) wrote:
>
> > It is not easy to find by itself (you have to do a lot of traceroutes)
> > so, if you have access to this information, it would be quite useful.
> >
> > (I'm one of the persons who see a lot of jitter for
> > j.root-servers.net with Randy Bush's experiment.)
>
> Well, either my probes don't pick up the jitter, or I'm guessing the
> naming convetion for j wrongly.
>
> I see
>
> jns1-hgtld.j.root-servers.net
> jns2-hgtld.j.root-servers.net
> jns3-hgtld.j.root-servers.net
> jns4-hgtld.j.root-servers.net
> jns5-hgtld.j.root-servers.net
> jns6-hgtld.j.root-servers.net
>
> (same from AS8495/AS8220 and AS8763)
>
> in alternating fashion, but I would assume "jns1" through "jns6" are
> just the individual servers of a setup called "hgtld".
Correct. At the moment, most J root instances are colocated with
com/net name servers. The instance you're reaching is colocated with
h.gtld-servers.net, which is in Amsterdam.
Matt
--
Matt Larson <mlarson@verisign.com>
VeriSign Naming and Directory Services
