IETF Logo Mail Archive

Re: [DNSOP] Anycast and DNS questions

"Patrick W. Gilmore" <patrick@ianai.net> Wed, 06 August 2014 12:10 UTC

Return-Path: <patrick@ianai.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D78F1A0252 for <dnsop@ietfa.amsl.com>; Wed, 6 Aug 2014 05:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AR0YFUH9FGtB for <dnsop@ietfa.amsl.com>; Wed, 6 Aug 2014 05:10:21 -0700 (PDT)
Received: from ianai.priori.net (bos2.priori.net [140.186.190.105]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE79C1A00C2 for <dnsop@ietf.org>; Wed, 6 Aug 2014 05:10:21 -0700 (PDT)
Received: from [192.168.1.172] (173-9-104-45-NewEngland.hfc.comcastbusiness.net [173.9.104.45]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: patrick) by ianai.priori.net (Postfix) with ESMTPSA id BFC1261E32; Wed, 6 Aug 2014 08:11:32 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: "Patrick W. Gilmore" <patrick@ianai.net>
X-Mailer: iPhone Mail (11D257)
In-Reply-To: <20140806114759.GF5546@cisco.com>
Date: Wed, 06 Aug 2014 08:10:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <25907D96-0076-417A-8DB9-41A5A178D479@ianai.net>
References: <20140806114759.GF5546@cisco.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/LRfJlLAJ1M6Oe47geaX2yHCR2yU
Subject: Re: [DNSOP] Anycast and DNS questions
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Aug 2014 12:10:23 -0000

Composed on a virtual keyboard, please forgive typos. 

On Aug 6, 2014, at 7:47, Toerless Eckert <eckert@cisco.com> wrote:
> 
> Sorry, haven't been following this group for a long time, so
> please excuse if answers to these questions have been discussed in before:
> 
> a) What documents beside RFC3258  are describing any uses/procedures
>   for having DNS servers use an anycast address to receive and respond to
>   requests ?

Dunno, but something tells me a quick BING search would return millions of answers. 

> b) How common are deployments in which the information returned by different
>   anycast member DNS servers for the same query would be different,
>   aka: to "localize" lookup results, such as pointing to
>   local CDN caches or the like ? What would be the most well known examples
>   of such deployed instances ?  Any IETF documents describing this ? Any
>   rules to follow ?

Common? Ridiculously so, for at least 20 years.

Well known examples?  CDNs, as you already mentioned. E.g. LLNW. 


> c) Any example in which the DNS servers utilizing a single shared
>   IP address (anycast address) are run by different operators ? Any
>   documents describing this ? (RFC3258 seems to focus on single operator
>   anycast group of DNS servers.

How about the root servers?

-- 
TTFN,
patrick

v2.29.0 | Report a Bug | By Email | System Status