From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lucas Barros <lucasbarros.kam@gmail.com>
Subject: applied: [PATCH common/manager v3 0/2] fix #6357: show all search domains in the node DNS settings
Date: Fri, 20 Nov 2026 12:50:36 +0100 [thread overview]
Message-ID: <179517543422.4183140.6472884238874649410.b4-ty@b4> (raw)
In-Reply-To: <20261116133000.6357-0-lucasbarros.kam@gmail.com>
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, thanks!
[manager]
[1/1] fix #6357: api: node dns: return all search domains
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=813a0d644e9fb613191ea0c2b197c06553c0b14a
prev parent reply other threads:[~2026-11-20 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 13:31 [PATCH common/manager v3 0/2] fix #6357: show all search domains in the node DNS settings Lucas Barros
2026-11-16 13:31 ` [PATCH common v3 1/2] inotify: resolv.conf: add reader that keeps the whole search list Lucas Barros
2026-11-16 13:31 ` [PATCH manager v3 2/2] fix #6357: api: node dns: return all search domains Lucas Barros
2026-11-18 1:42 ` partially-applied: [PATCH common/manager v3 0/2] fix #6357: show all search domains in the node DNS settings Thomas Lamprecht
2026-11-20 11:50 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179517543422.4183140.6472884238874649410.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=lucasbarros.kam@gmail.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox