From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 8E75B9DAF9 for ; Fri, 24 Nov 2023 15:56:18 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7179411B5E for ; Fri, 24 Nov 2023 15:56:18 +0100 (CET) Received: from lana.proxmox.com (unknown [94.136.29.99]) by firstgate.proxmox.com (Proxmox) with ESMTP for ; Fri, 24 Nov 2023 15:56:17 +0100 (CET) Received: by lana.proxmox.com (Postfix, from userid 10043) id 58D462C119E; Fri, 24 Nov 2023 15:56:16 +0100 (CET) From: Stefan Hanreich To: pve-devel@lists.proxmox.com Date: Fri, 24 Nov 2023 15:56:15 +0100 Message-Id: <20231124145615.332941-1-s.hanreich@proxmox.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.420 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH pve-docs] sdn: dhcp: document changes in default configuration of dnsmasq X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2023 14:56:18 -0000 The layout of the configuration folder has changed before release, update the documentation to reflect those changes. Also add a tip about automatic name resolution to the documentation. Signed-off-by: Stefan Hanreich --- pvesdn.adoc | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/pvesdn.adoc b/pvesdn.adoc index fdc6ea7..5c25a3e 100644 --- a/pvesdn.adoc +++ b/pvesdn.adoc @@ -675,12 +675,10 @@ folder `/etc/dnsmasq.d/`: `00-default.conf`:: This contains the default global configuration for a dnsmasq instance. -`10--.conf`:: -This file configures specific options for a subnet, such as the DNS server that -should get configured via DHCP. - -`10--.ranges.conf`:: -This file configures the DHCP ranges for the dnsmasq instance. +`10-.conf`:: +This file configures specific options for a VNet, such as the DNS server that +should get configured via DHCP. It also configures the different Subnets +included in a VNet as well as their DHCP ranges. `ethers`:: This file contains the MAC-address and IP mappings from the IPAM plugin. In @@ -702,6 +700,11 @@ For more information please consult the documentation of xref:pvesdn_ipam_plugin_pveipam[the PVE IPAM plugin]. Changing DHCP leases is currently not supported for the other IPAM plugins. +TIP: The default configuration of dnsmasq automatically provides name +resolution for the hostnames of the guests. It should be automatically set as +DNS server for the guests via DHCP, so you can reach other guests in the simple +zone via their hostname. + [[pvesdn_setup_examples]] Examples -------- -- 2.39.2