[Add] TTL of resolver.arpa
Daniel Migault <mglt.ietf@gmail.com> Wed, 22 December 2021 14:45 UTC
Return-Path: <mglt.ietf@gmail.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A424D3A0029 for <add@ietfa.amsl.com>; Wed, 22 Dec 2021 06:45:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 l2x5gMfldxuG for <add@ietfa.amsl.com>; Wed, 22 Dec 2021 06:45:24 -0800 (PST)
Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com [IPv6:2607:f8b0:4864:20::92f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 101353A0028 for <add@ietf.org>; Wed, 22 Dec 2021 06:45:23 -0800 (PST)
Received: by mail-ua1-x92f.google.com with SMTP id y22so4815228uap.2 for <add@ietf.org>; Wed, 22 Dec 2021 06:45:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=rO3jSjdaVVGwbFp306D0Zt35bhPspDsON+5d4EU3TWo=; b=pr2+WHjS3nBht/udjnPjNV0Cvjewaq4wsDoJMTYdXtNRX5hiuDZgYVmKqP6n+PPCcT dieNKWrH392JmIDYkYMGWIAjNo1TG4eNCEzHfnqYRQ+eTpJ9g0lmdySLCQAM+yoo1+IX DLE4rmcvK9OOTzfb08O3M6tGDaCfJP9PG+4rrt/sy9j/7gCzonN9yr45uU4dGaTxOMYu bAan7E49cB9eRwIY+EpdasmGbZugevPMQlWFzmHniLKY5A/fGjCnBReYcGC37yGAr1BP 7GQ2KlLN1zw9zhmapqp/GWaGvtyT6smtUi968hMn00PuYRphQu0EUGUBPte/9Nrf7WRl Cl0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=rO3jSjdaVVGwbFp306D0Zt35bhPspDsON+5d4EU3TWo=; b=FEzg+HuxacohwNkVjgj0IQpm12OLk6lps0nOXcjPQN7E8s3fxtZwag3Sp18DyKRDB2 do45aDzPDNFKpXJZ4UqVIskWUvK9WLK71EmCfhL/DQGru6w6dab+atP2ANQhRwziMLOf 5sOby2OLLHelwR1sa6nlitare7pROprPpu6mM18wVYSKW/LsW1k/2eTEqWnpd0jn0BCz N9+BhUO8PTOh9L9L6vODCPicmU6OWPSrPVolzcXVc2jq2fMeAjV+y4utXSkSR9AioizC HBjKbPLvl2v0tX8WPeCvrODWndWjHD0PX379k7DuNuapAy+AB0M/r0wRQPM27u4xsGmW rHDQ==
X-Gm-Message-State: AOAM531I3pyjVV3GHnFF6sA17/sd/Sfiw0bNVNt1Ip8pkcWnbY/k/G/G yzKjl2+JfXQfQMButZ0FKlvpaIcWZKb0/cQxYPincBrlq94=
X-Google-Smtp-Source: ABdhPJyyRF/MobOukbWsxwU4gMB97JOv6JHeKyDBDaDhb96zzST1X2wX0qLivc4ZRIQU9Z+lFEK2RSwJ3KqXbaG2ULM=
X-Received: by 2002:a9f:2329:: with SMTP id 38mr951664uae.124.1640184321661; Wed, 22 Dec 2021 06:45:21 -0800 (PST)
MIME-Version: 1.0
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Wed, 22 Dec 2021 09:45:11 -0500
Message-ID: <CADZyTkmMKJ=shoWZxEUeyt8vNAs6SWHOr9BGkr-+63=Gcv934w@mail.gmail.com>
To: ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dbfd3b05d3bd2b2a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/Y7p9EJE6uYYhqXc6ChQlYOxNn0Y>
Subject: [Add] TTL of resolver.arpa
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Dec 2021 14:45:29 -0000
Hi, I am wondering if some additional text is not needed regarding the TTL of the _dns.resolver.arpa RRset. As resolver.arpa is not owned by anyone, this information should not be cached. If one device is changing network for example, we should make sure the mobile will not consider the resolver.arpa response performed on a previous network. Similarly, when a dns client performs simultaneous discovery on different resolvers. Should we recommend/mandate the DNS client to set this TTL to 0 and not cache the response ? _dns.resolver.arpa 7200 IN SVCB 1 doh.example.net ( alpn=h2 dohpath=/dns-query{?dns} ) Yours, Daniel -- Daniel Migault Ericsson
- [Add] TTL of resolver.arpa Daniel Migault
- Re: [Add] TTL of resolver.arpa Eric Orth
- Re: [Add] TTL of resolver.arpa Paul Wouters
- Re: [Add] [EXTERNAL] Re: TTL of resolver.arpa Tommy Jensen
- Re: [Add] [EXTERNAL] Re: TTL of resolver.arpa Paul Wouters
- Re: [Add] [EXTERNAL] Re: TTL of resolver.arpa Daniel Migault
- Re: [Add] [EXTERNAL] Re: TTL of resolver.arpa Ben Schwartz
- Re: [Add] [EXTERNAL] Re: TTL of resolver.arpa Tommy Jensen
- Re: [Add] [EXTERNAL] Re: TTL of resolver.arpa Daniel Migault
- Re: [Add] [EXTERNAL] Re: TTL of resolver.arpa Steffen Nurpmeso