[62422] in North American Network Operators' Group
Re: DNS anycast considered harmful (was: .ORG problems this evening)
daemon@ATHENA.MIT.EDU (Stephen J. Wilcox)
Thu Sep 18 09:09:29 2003
Date: Thu, 18 Sep 2003 13:07:23 +0000 (GMT)
From: "Stephen J. Wilcox" <steve@telecomplete.co.uk>
To: Todd Vierling <tv@duh.org>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>,
Iljitsch van Beijnum <iljitsch@muada.com>, <nanog@merit.edu>
In-Reply-To: <Pine.NEB.4.58.0309180825200.3593@server.duh.org>
Errors-To: owner-nanog-outgoing@merit.edu
> : > There's an easy fix to that particular situation: Make the first (or first
> : > two) listed servers anycast, and the rest unicast.
> :
> : It would require a central management (or at least a central
> : oversight) of the root name servers and I do not believe there is one:
> : each root name server anycasts at will, without a leader saying ("A
> : and B will anycast, the others will stay unicast").
>
> Well, that's something for the root server operators to think about and
> discuss amongst themselves. I know several of them are reading this list,
> and may be reading this thread. 8-)
Plus, A is verisign so any hopes of cluefulness or working for the community are
fading fast!
> Still doesn't help .ORG, which is 100% anycast and thus has no DNS-based
> redundancy (see my experience elsewhere in this thread).
It does - there are two! Yuo just mean less than 13 as per the root.
What is the maximum number you can fit in a single NS reply for a 3 letter tld
such as .com/.org ? (Is it still 13? I'm not familiar with the DNS protocol at
that level)
Steve
