DNS query reliability (was Re: The internet architecture)

Dave CROCKER <dhc2@dcrocker.net> Sun, 07 December 2008 07:54 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 341A13A67D1; Sat, 6 Dec 2008 23:54:48 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DB393A67D1 for <ietf@core3.amsl.com>; Sat, 6 Dec 2008 23:54:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.607
X-Spam-Level:
X-Spam-Status: No, score=-1.607 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJCN2Kh1oY5u for <ietf@core3.amsl.com>; Sat, 6 Dec 2008 23:54:46 -0800 (PST)
Received: from s-utl01-sjpop.stsn.net (s-utl01-sjpop.stsn.net [72.254.0.201]) by core3.amsl.com (Postfix) with SMTP id 785AA3A67B6 for <ietf@ietf.org>; Sat, 6 Dec 2008 23:54:45 -0800 (PST)
Received: from s-utl01-sjpop.stsn.net ([127.0.0.1]) by s-utl01-sjpop.stsn.net (SMSSMTP 4.1.2.20) with SMTP id M2008120623543809371 ; Sat, 06 Dec 2008 23:54:38 -0800
Received: from [10.58.58.27] ([10.58.58.27]) by s-utl01-sjpop.stsn.net; Sat, 6 Dec 2008 23:54:37 -0800
Message-ID: <493A8AC6.3050204@dcrocker.net>
Date: Sat, 06 Dec 2008 06:23:02 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: Andrew Sullivan <ajs@shinkuro.com>
Subject: DNS query reliability (was Re: The internet architecture)
References: <C15AE32B-E564-4C93-86FF-40EF203E673A@mpi-sws.org> <49382030.5020704@network-heretics.com> <2788466ED3E31C418E9ACC5C316615572FFBEF@mou1wnexmb09.vcorp.ad.vrsn.com> <49384BCF.2080600@network-heretics.com> <2788466ED3E31C418E9ACC5C316615572FFBF3@mou1wnexmb09.vcorp.ad.vrsn.com> <493850D8.7090908@network-heretics.com> <20081205133133.GC14834@nic.fr> <4939392F.6090004@network-heretics.com> <20081205174658.GD4148@shinkuro.com>
In-Reply-To: <20081205174658.GD4148@shinkuro.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


Andrew Sullivan wrote:
> It seems to me true, from experience and from anecdote, that DNS out
> at endpoints has all manner of failure modes that have little to do
> with the protocol and a lot to do with decisions that implementers and
> operators made, either on purpose or by accident. 
...
> This suggests to me that there will be an opportunity to improve some
> of the operations in the wild,
...
> If you have a cache of these examples, I'd be delighted to see them.


One could imagine producing a BCP about common DNS implementation and operation 
errors or, more positively, recommendations for implementation and operation.

One could equally imagine some group actively pursuing improvements to the major 
implementations (and operations) that have problems.

I seem to recall seeing small forays in this direction, in the past.  Your query 
might encourage an organized effort that follows through with making actual DNS 
operation -- as opposed to attack or defense of the protocol -- provide the 
needed level of *end-to-end* reliability.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf