From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id A8EFE1FF0C0 for ; Wed, 18 Nov 2026 02:43:15 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 9511721632; Wed, 18 Nov 2026 02:43:11 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Lucas Barros Subject: partially-applied: [PATCH common/manager v3 0/2] fix #6357: show all search domains in the node DNS settings Date: Wed, 18 Nov 2026 02:42:33 +0100 Message-ID: <179496614881.1570915.948232962367863040.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261116133000.6357-0-lucasbarros.kam@gmail.com> References: <20261116133000.6357-0-lucasbarros.kam@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794966185891 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.192 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: MJ737DRXATHMTHWSDIMP2ZOUBR3UZDLX X-Message-ID-Hash: MJ737DRXATHMTHWSDIMP2ZOUBR3UZDLX X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 16 Nov 2026 10:31:06 -0300, Lucas Barros wrote: > The DNS settings of a node only show the first domain of the 'search' > line of resolv.conf, so saving the dialog again drops the others. > > As suggested by Thomas, v3 keeps the 'resolvconf' parser as it is, as > PVE and PMG use its value to build the FQDN of the node certificate and > more. It adds a new reader that keeps the whole search list, and only > the node DNS API uses it. > > [...] Applied the common part for now: [common] [1/1] inotify: resolv.conf: add reader that keeps the whole search list https://git.proxmox.com/?p=pve-common.git;a=commitdiff;h=9fb3e39d89414858fd3b7a57d07cec4c8a7c894e