bmanning at isi.edu
Tue Feb 25 10:41:29 UTC 2014
Peter, the isolation of anycast nodes is not at attribute of the DNS protocol, it is strictly a manipulation of the routing system,
the DNS -design- using the “belt-suspenders”/root-hints file to bootstrap priming queries, is expected to be globally reachable.
From a DNS perspective, they _are_ expected to answer queries from anywhere. When you tweak the routing system to not forward
packets, thats not DNS. But yes, its a fine point and very much technical in nature - perhaps not the right fodder for this list.
Neca eos omnes. Deus suos agnoscet.
On 25February2014Tuesday, at 2:23, Peter Koch <pk at ISOC.DE> wrote:
> On Mon, Feb 24, 2014 at 10:11:11PM -0800, manning bill wrote:
>> By definition, a root server, serves the global Internet, is designed to respond to queries generated from -EVERYWHERE- on the global Internet.
> we know that you know that this is true for the letter (as in, e.g., "B")
> but not necessarily for a particular instance of the letter in an anycast cloud(*).
> In fact, the various anycast operational models allow for more or less sharply
> bounded coverage, especially within a single AS. Such instances are _not_
> expected to answer queries from everywhere, simply because they are not
> expected to receive the traffic in the first place.
> It's already hard enough to separate the wheat from the chaff.
> (*) for those that do deploy anycast
> discuss mailing list
> discuss at 1net.org
More information about the discuss