From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id AF9C53858CD1 for ; Tue, 12 Mar 2024 06:45:30 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org AF9C53858CD1 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org AF9C53858CD1 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710225933; cv=none; b=T9n5i0ATX54u0GwpcB//IFHs24aqrrT1ZSRtVLZWaBt59P5C1Dwmbsd6btkWVeYpu78IAgVFb6q96B5Adg6OpU1HV4S+l+FLnfYseidvFGwR6WSGuh6LUgm95THtdrUvoSpQXHFfVIk1MuL2BLrsukvsy8MEzaQXv6aaWFZPS3Y= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710225933; c=relaxed/simple; bh=Ot5BC+myHxEVa0GFaupPyMlrYbfH/qA0UzQZEEpGdYI=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=bKLK4Sr/Oa6gsO9BTvopQ0BABxZHaOMhgSHefgwNz3JJGFSb2IUcEKocwSeaylz8XPiQAACW0DWrou3nYJJ/foS9bN59hABcKqUqe2yZ9Dvin4EZCMe6xZIAwPp8fPTbid/hkExn63BX0EwBB3YWWSWnrO5qeDNdDH/DTsGzqzs= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1710225930; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iXIqhXw7PdUsXeRzwgqy4ypfuSr+h96RIkTzYVIIw18=; b=LrRPon7VMEYAJKt3JDWie5bQxornAsrCIkcy753+QHsxNn/5sbWHFxtBnh/aPnIVP6U1d1 tyijkmUN1Bn8BJq3/pbAJiafXR6Z8VjZUOA25HTNcvWNHula8UTsTkFPAlwhC//2velvGC 5mBIvqo1RF20zBbAYsS+XPwgbMF5r/k= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-99-NgvB6c7FMqm7A59_R-_APQ-1; Tue, 12 Mar 2024 02:45:26 -0400 X-MC-Unique: NgvB6c7FMqm7A59_R-_APQ-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 90F923803900; Tue, 12 Mar 2024 06:45:26 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.73]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9F860492BD1; Tue, 12 Mar 2024 06:45:25 +0000 (UTC) From: Florian Weimer To: Cristian =?utf-8?Q?Rodr=C3=ADguez?= Cc: John Levon , libc-alpha@sourceware.org Subject: Re: Issue with stale resolv.conf state References: <874jddqbx4.fsf@oldenburg.str.redhat.com> Date: Tue, 12 Mar 2024 07:45:23 +0100 In-Reply-To: ("Cristian =?utf-8?Q?Rodr=C3=ADguez=22's?= message of "Mon, 11 Mar 2024 21:51:44 -0300") Message-ID: <87ttlcvth8.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.10 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-5.2 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: * Cristian Rodr=C3=ADguez: > On Mon, Mar 11, 2024 at 7:51=E2=80=AFAM Florian Weimer wrote: >> >> * John Levon: >> > cessing). >> >> Maybe we should just remove the automatic downgrade, basically not >> persist this across queries anymore. > > Yeah. +1. Users of those broken nameservers deserve at least noticing > they are wrong if such systems are really still around .. I filed: Automatic activation of single-request options break resolv.conf reloadin= g On the other hand, we have this request: | Change resolv.conf default to single-request | [=E2=80=A6] | We have the year 2022 and these issues still occur, so it was not some | kind of issue that went away by time as it was possibly expected when | glibc 2.10 was released. So the solution might not be so straightforward. Thanks, Florian