[80590] in North American Network Operators' Group
Re: [dnsop] DNS Anycast revisited (fwd)
daemon@ATHENA.MIT.EDU (Edward B. Dreger)
Wed May 4 09:52:42 2005
Date: Wed, 4 May 2005 13:52:16 +0000 (GMT)
From: "Edward B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Tony Finch <dot@dotat.at>
Cc: nanog@merit.edu
In-Reply-To: <Pine.LNX.4.60.0505041047070.5283@hermes-1.csi.cam.ac.uk>
Errors-To: owner-nanog@merit.edu
TF> Date: Wed, 4 May 2005 10:48:56 +0100
TF> From: Tony Finch
TF> Why would anyone use an anycast address as a client? Wouldn't it be
TF> simpler to make all client connections from the machine's unicast address?
Maybe, maybe not.
Take an anycast DNS provider that AXFR/IXFRs zones from its customers.
Notifying them of all anycast addresses and keeping ACLs up-to-date
isn't feasible.
The obvious answer is to have a couple hosts pull zones from unicasted
addresses. However, this creates a few small targets... the question is
if DNS slaves would benefit sufficiently from increased splay to warrant
the additional implementation complexity.
Eddy
--
Everquick Internet - http://www.everquick.net/
A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 785 865 5885 Lawrence and [inter]national
Phone: +1 316 794 8922 Wichita
________________________________________________________________________
DO NOT send mail to the following addresses:
davidc@brics.com -*- jfconmaapaq@intc.net -*- sam@everquick.net
Sending mail to spambait addresses is a great way to get blocked.
Ditto for broken OOO autoresponders and foolish AV software backscatter.
