IETF Logo Mail Archive

Re: [DNSOP] New draft on delegation revalidation

Stephane Bortzmeyer <bortzmeyer@nic.fr> Sat, 11 April 2020 16:33 UTC

Return-Path: <stephane@sources.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CDF43A14DE for <dnsop@ietfa.amsl.com>; Sat, 11 Apr 2020 09:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level:
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 182pIgvjHFFH for <dnsop@ietfa.amsl.com>; Sat, 11 Apr 2020 09:33:09 -0700 (PDT)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [92.243.4.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF7503A14DD for <dnsop@ietf.org>; Sat, 11 Apr 2020 09:33:09 -0700 (PDT)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id 2EA19A0277; Sat, 11 Apr 2020 18:33:07 +0200 (CEST)
Received: by mail.sources.org (Postfix, from userid 1000) id D7B35CAE6A; Sat, 11 Apr 2020 18:30:41 +0200 (CEST)
Date: Sat, 11 Apr 2020 18:30:41 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Shumon Huque <shuque@gmail.com>
Cc: Brian Dickson <brian.peter.dickson@gmail.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>
Message-ID: <20200411163041.GA16482@sources.org>
References: <CAHPuVdV9eSCLQOqMF0cq8fHcuSZs7nCgjhHMfMoaV5H=ekbtSA@mail.gmail.com> <CAH1iCiqcdQCDs0gY=+zJdkfLx4+mbEAzSZp1hPJuyM5U0KTAiQ@mail.gmail.com> <CAHPuVdUjsC62TK-4WeaL-TWgBpz_qk7mQb=JqGQd5U_djXNA3Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAHPuVdUjsC62TK-4WeaL-TWgBpz_qk7mQb=JqGQd5U_djXNA3Q@mail.gmail.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 10.3
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jdSLy11VYsoqOyoBS1Y1Wp-YjVA>
Subject: Re: [DNSOP] New draft on delegation revalidation
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 11 Apr 2020 16:33:11 -0000

On Sat, Apr 11, 2020 at 09:22:42AM -0400,
 Shumon Huque <shuque@gmail.com> wrote 
 a message of 138 lines which said:

> > The delegation (re)validation might be a reasonable place to
> > implement something to detect this and adjust the choice of NS on
> > the resolver's cache.
> 
> I think most resolvers do a bit of this today already. If they detect a
> broken delegation, they will mark that server as lame, and remove it from
> the candidate nameservers for the zone (for a certain period of time), and
> try another one.

I don't think that you answer Brian's idea. The way I've read his
idea, he suggested, when a resolver detects a lame server (or when all
servers are lame?), to go back to the parent and to ask again the NS
set, to see if there is a new and better list.

v2.23.0 | Report a Bug | By Email